This is the mail archive of the
mailing list for the Cygwin project.
RE: [BUG] Nasty bug persists on x86-64
- From: Pavel Fedin <p dot fedin at samsung dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 02 Sep 2014 11:06:15 +0400
- Subject: RE: [BUG] Nasty bug persists on x86-64
- Authentication-results: sourceware.org; auth=none
- References: <007601cfc5ef$09e5bb60$1db13220$%fedin at samsung dot com> <20140901152634 dot GA18880 at calimero dot vinschen dot de>
> Try `bt' at this point. Maybe the backtrace shows something of
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 :(
Samsung Electronics Research center Russia
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple