Robert Kiesling wrote:
? I don't know what this means but Windows has the equivalent of SIGSEGV.
The signal is non-catchable by UNIX apps. That ability would
be useful when malloc goes whizzing off into the video RAM, but
the issue is almost always a bug somewhere else in the app. That
is not to say that the system libraries are perfect, of course.
Um... I can catch SIGSEGV just fine in my UNIX apps. Or did you mean
cygwin apps can't catch it? (Granted, I don't attempt to *recover* from
a SEGV, just say "hey, I got a SEGV" and either exit() or abort().)
--
Matthew
Cannot read .sig now
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
