On Sun, Jul 5, 2009 at 1:50 PM, Dave Korn<dave.korn.cyg...@googlemail.com> wrote: > Actually even more useful would be to know what Cygwin DLL version you're > running. The problems page that CGF directed you to contains in particular > the advice to run "cygcheck -s -v -r > cygcheck.out" and then send the > cygcheck.out file ** as an attachment, not inline, please ** to the list with > your post.
Done. > Well, what happened was that there's a bug somewhere, and while cygwin was > in the process of dumping the stack trace for the abort caused by your > assertion firing, the DLL itself had a segfault, and had to give up. It said > "probably corrupted stack", because that's the most common reason why you > might end up following a stray pointer and causing a segfault when you were > trying to unwind the stack, but in this case it's unlikely anything would have > corrupted the stack, so either there's a real bug or perhaps just some kind of > frame-pointer optimisation that confuses the unwind routine. I was building my test programs without any optimizations, but with -g option set. Regards, Roman Werpachowski
cygcheck.out
Description: Binary data
-- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
