This is the mail archive of the
mailing list for the Cygwin project.
- From: Jon TURNEY <jon dot turney at dronecode dot org dot uk>
- To: Ken Brown <kbrown at cornell dot edu>, cygwin at cygwin dot com
- Date: Thu, 23 Oct 2014 12:31:05 +0100
- Subject: Re: Threads
- Authentication-results: sourceware.org; auth=none
- References: <54450835 dot 3050602 at cornell dot edu>
On 20/10/2014 14:03, Ken Brown wrote:
Or is there some other plausible explanation for "impossible" crashes?
This can't just be a result of a gdb bug, because in at least one case
the assertion can be shown to be valid by using printf instead of gdb.
[*] By "impossible" I mean that examination of the relevant variables in
gdb shows that the assertions are in fact true. Two ongoing examples are
As a suggestion, you might want to also take a careful look at how
signal delivery is implemented in cygwin on x86_64
I had a vague idea that there was, at some time in the past, a fix made
for register corruption on x86_64 after a signal was handled, but I
can't find it now, so maybe I imagined it. But if for e.g. the flags
register was getting corrupted when a signal interrupts the main thread,
that could perhaps also explain what is being seen.
(More generally, it doesn't have to be another thread which is causing
these problems, it could be some form of interrupt)
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple