> I just checked in a fix which should keep the stack trace going even > when it finds a return address of zero.
> It will be in the next cygwin snapshot at: http://cygwin.com/snapshots/ > but be advised that this is a 1.7.x version of Cygwin and there ar > changes to the way mounts are handled in this new version as well as > other incompatibilies with the current stable 1.5.x series. So, if > you use it, please research the differences by reading the cygwin > mailing list archives. I have similar problem , and I would like to get fix for this. However - I have latest stable cygwin1.dll as v1.5, and trying to replace it with v1.7 produces more problems. Would it be possible to tell me what needs to be changed and where - may be we could try to patch v1.5 only with that backtrace support, no other changes ? Or do I somehow upgrade whol cygwin ? -- View this message in context: http://www.nabble.com/seg-fault-produces-stackdump-with-no-stack-trace-tp18777069p22994946.html Sent from the Cygwin list mailing list archive at Nabble.com. -- 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/
