On Wed, May 16, 2007 at 04:15:54PM -0700, Alex Shturm wrote:
>The description of proc_retry:n did not mention this requirement.
It is a general requirement for the CYGWIN environment variable.
>Anyway, after I defined my CYGWIN variable in
>My Computer > Properties > Advanced > Environment Varia
Christopher,
The description of proc_retry:n did not mention this requirement.
Anyway, after I defined my CYGWIN variable in
My Computer > Properties > Advanced > Environment Variables,
everything worked fine!
Thanks a lot for your help!
Alex
>It did not help... :(
>The program still rest
On Wed, May 16, 2007 at 01:26:07PM -0700, Alex Shturm wrote:
>It did not help... :(
>The program still restarts 5 times...
You did set it before running any cygwin shell, right?
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/proble
It did not help... :(
The program still restarts 5 times...
Christopher Faylor wrote:
On Wed, May 16, 2007 at 12:31:58PM -0700, Alex Shturm wrote:
Wow.
Is it a documented behavior?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
See the "proc_retry" entry. It neglects to mentio
On Wed, May 16, 2007 at 12:31:58PM -0700, Alex Shturm wrote:
>Wow.
>Is it a documented behavior?
http://cygwin.com/cygwin-ug-net/using-cygwinenv.html
See the "proc_retry" entry. It neglects to mention that the default is
10.
You might be able to set CYGWIN=proc_retry:1 but it's possible that
Cy
Wow.
Is it a documented behavior?
What is the reason for cygwin to believe that the program needs to be
re-run?
I'm not sure how I can control the exit value if the actual exit is
performed by exception handler...
Thanks,
Alex
Christopher Faylor wrote:
Actually, nevermind. I know what the
On Wed, May 16, 2007 at 03:13:07PM -0400, Christopher Faylor wrote:
>On Wed, May 16, 2007 at 11:57:30AM -0700, Alex Shturm wrote:
>>Christopher,
>>
>>I agree there is a misunderstanding here.
>>Please see my original post - there I clearly say that I build this
>>program in Visual Studio 2005, and
On Wed, May 16, 2007 at 11:57:30AM -0700, Alex Shturm wrote:
>Christopher,
>
>I agree there is a misunderstanding here.
>Please see my original post - there I clearly say that I build this
>program in Visual Studio 2005, and not using gcc.
SORRY. I completely misread the "run this program under
Christopher,
I agree there is a misunderstanding here.
Please see my original post - there I clearly say that I build this
program in Visual Studio 2005, and not using gcc.
I only have problems *running* it under cygwin.
Thanks,
Alex
Christopher Faylor wrote:
On Wed, May 16, 2007 at 11:14:3
On Wed, May 16, 2007 at 11:14:36AM -0700, Alex Shturm wrote:
>cgf wrote:
>>Cygwin uses the equivalent of SetUnhandledExceptionFilter for its own
>>purposes. It can do that because there is no linux version of that
>>function.
>>
>>So, if you attempt to use it in a cygwin-aware program, you're in f
Christopher,
Cygwin uses the equivalent of SetUnhandledExceptionFilter for its own
purposes. It can do that because there is no linux version of that
function.
So, if you attempt to use it in a cygwin-aware program, you're in for
problems. If you need to produce pure windows programs, I'd sugg
On Tue, May 15, 2007 at 11:52:50PM -0700, Alex Shturm wrote:
>Hello,
>
>This is a simple program that I compile as a console application in
>Visual Studio 2005 :
>--
>#include
>#include
>
>LONG WINAPI my_exception_filter (LPEXCEPTION_POINTERS exception
Hello,
This is a simple program that I compile as a console application in
Visual Studio 2005 :
--
#include
#include
LONG WINAPI my_exception_filter (LPEXCEPTION_POINTERS exceptionInfo)
{
printf ("*** my_exception_filter ***\n");
return EXCEPTION_E
13 matches
Mail list logo
