[BUG] Nasty bug persists on x86-64
Pavel Fedin
p.fedin@samsung.com
Tue Sep 2 07:06:00 GMT 2014
Hello Corinna!
> Try `bt' at this point. Maybe the backtrace shows something of
> interest.
You haven't read the message completely. 'bt' cannot help since there's no debug information for ntdll and gdb is unable to unwind the stack correctly.
> Apart from that, try the latest snapshot from
> https://cygwin.com/snapshots/ I converted the internal exception
> handling avoiding crashes from system functions to SEH. Perhaps the
> above doesn't show up with it.
I have installed the snapshot, and looks like it's now stable. However, this exception actually persists. I can tell you some more details. The actual malfunction happens when this exception fires twice in a row. I managed to catch this with strace a couple of times, but didn't save logs unfortunately.
I want to try to bisect for the origin of this crash. Currently i know that it happens before main(). But is main() a real entry point ? I believe it's not. Can you tell me what is the real binary's entry point in Cygwin ?
Yesterday in the evening i replied from home with some more information, but my reply got lost again :(
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
--
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
More information about the Cygwin
mailing list