On Fri, Sep 07, 2007 at 04:17:30PM -0500, Matthew Woehlke wrote: > 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().)
Cygwin can catch SIGSEGV just fine. So can Windows. I don't want to belabor the point but there isn't much that makes sense to me here, especially in context of the subject. cgf -- 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/
