I do not run a debugger, but I do run dbwin32 (it fetches all debug output
and prints it in a window) so I see all OutputDebugStrings.
With a SEGV you normally get the dialogbox "The application has encountered
a problem...." so that should be visisble, it should also generate a dump
with Dr.Watson and there is none.
----- Original Message -----
From: "Greg Chicares" <chicares@...>
Sent: Tuesday, April 18, 2006 2:22 PM
Subject: Re: [Mingw-users] Strange crash/application exit...
> On 2006-4-18 11:35 UTC, mikael-aronsson wrote:
>> I have an application running at a customers computer (I cannot run gdb
>> on it at the moment) and after a few days the application vanishes from
>> the computer, it is simply not running any more. (there is no logic in
>> it, no specific time, sometimes after 2 days sometimes after 5, it is
>> not eating memory, I have debug output of the memory statistics and
>> there is plenty of ram available at all times even the seconds before it
>> is gone).
> I'd guess it's a SEGV.
>> I have added both:
>> atexit( exit_handler); and
> That would be called only upon normal termination.
>> signal( SIGABRT, abort_handler);
> I think that means only that the abort() function was not called.
> There are other signals that would need to be handled on a posix
> platform, but generally they don't work on msw:
>> and put OutputDebugString() in both to
>> see when they get called....
> But you're not running a debugger, so that won't do anything.
> unless the system provides one. I'd try drmingw; its documentation
> may be helpful even if you use a different debugger.
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> that extends applications into web and mobile media. Attend the live
> and join the prime developer group breaking into this new coding
> MinGW-users mailing list
> You may change your MinGW Account Options or unsubscribe at: