From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Intermittent failures retrieving process exit codes - snapshot test requested
Date: Tue, 01 Jan 2013 05:36:00 -0000 [thread overview]
Message-ID: <20130101053606.GB18911@ednor.casa.cgf.cx> (raw)
In-Reply-To: <50E23F98.1060004@coverity.com>
On Mon, Dec 31, 2012 at 08:44:56PM -0500, Tom Honermann wrote:
>On 12/29/2012 04:57 PM, Christopher Faylor wrote:
>> On Thu, Dec 27, 2012 at 03:49:24PM -0500, Tom Honermann wrote:
>>> When interrupting the test run, I'll often (but not always) get the
>>> following error:
>>>
>>> c:\>test-strace.bat
>>> test...
>>> test...
>>> test...
>>> test...
>>> --- Process 8092, exception 40010005 at 75E26D67
>>
>> That is coming from strace and it's:
>>
>> /usr/include/w32api/ntstatus.h:#define DBG_CONTROL_C ((NTSTATUS)0x40010005)
>>
>> i.e., it's expected.
>
>Ah, sorry, I should have researched that further before reporting it.
>Thanks for the explanation.
>
>>> Additionally, some of the Cygwin gcc built utilities that I've built for
>>> testing now occasionally hang upon interruption by ctrl-c. Basic
>>> diagnostics courtesy of gdb follow.
>>
>> The hang should be fixed in the latest snapshot.
>
>I'm still seeing hangs in the latest code from CVS. The stack traces
>below are from WinDbg.
I'm not asking you to build this yourself. I have no way to know how
you are building this. Please just use the snapshots at
http://cygwin.com/snapshots/
>I manually resolved the symbol references within
>the cygwin1 module using the linker generated .map file. Since the .map
>file does not include static functions, some of these may be incorrect -
>I didn't try and verify or correct for this.
Thanks for trying, but the output below is garbled and not really
useful. If you are not going to dive in and attempt to fix code
yourself then all we normally need is a simple test case. WinDbg
is not really appropriate for debugging Cygwin applications.
cgf
> # ChildEBP RetAddr
>00 00288bd0 758d0a91 ntdll!ZwWaitForSingleObject+0x15
>01 00288c3c 76c11194 KERNELBASE!WaitForSingleObjectEx+0x98
>02 00288c54 76c11148 kernel32!WaitForSingleObjectExImplementation+0x75
>03 00288c68 610f1553 kernel32!WaitForSingleObject+0x12
>04 00288cb8 6118e54d cygwin1!strtosigno+0x357
> __ZN4muto7acquireEm
> muto::acquire(unsigned long)
>[snip]
--
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
next prev parent reply other threads:[~2013-01-01 5:36 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 19:55 Intermittent failures retrieving process exit codes Tom Honermann
2012-12-07 21:54 ` Tom Honermann
2012-12-07 23:07 ` bartels
2012-12-21 6:30 ` Tom Honermann
2012-12-21 10:33 ` Corinna Vinschen
2012-12-21 12:15 ` Nick Lowe
2012-12-21 19:45 ` Tom Honermann
2012-12-22 3:09 ` Nick Lowe
2012-12-21 16:10 ` Christopher Faylor
2012-12-21 17:02 ` Corinna Vinschen
2012-12-21 19:36 ` Intermittent failures retrieving process exit codes - snapshot test requested Christopher Faylor
2012-12-21 20:37 ` Daniel Colascione
2012-12-21 22:23 ` marco atzeri
2012-12-21 23:09 ` Tom Honermann
2012-12-22 2:53 ` Christopher Faylor
2012-12-22 2:57 ` Tom Honermann
2012-12-22 2:49 ` Christopher Faylor
2012-12-22 3:14 ` Christopher Faylor
2012-12-22 9:06 ` marco atzeri
2012-12-22 17:50 ` Christopher Faylor
2012-12-23 16:56 ` Christopher Faylor
2012-12-23 18:54 ` marco atzeri
2012-12-27 20:50 ` Tom Honermann
2012-12-29 21:57 ` Christopher Faylor
2013-01-01 1:45 ` Tom Honermann
2013-01-01 5:36 ` Christopher Faylor [this message]
2013-01-02 19:15 ` Tom Honermann
2013-01-02 20:48 ` Christopher Faylor
2013-01-02 20:53 ` Daniel Colascione
2013-01-02 21:41 ` Christopher Faylor
2013-01-02 21:25 ` Tom Honermann
2013-01-15 22:17 ` Intermittent failures with ctrl-c (was: retrieving process exit codes) Tom Honermann
2013-01-16 2:04 ` Christopher Faylor
2013-01-16 16:38 ` Intermittent failures with ctrl-c Tom Honermann
2013-01-16 16:53 ` marco atzeri
2013-01-16 17:42 ` Tom Honermann
2013-01-16 18:05 ` Earnie Boyd
2013-01-16 18:51 ` Tom Honermann
2013-01-16 18:59 ` Christopher Faylor
2013-01-16 20:19 ` Tom Honermann
2013-01-16 22:23 ` Christopher Faylor
2013-01-18 20:12 ` Tom Honermann
2013-01-19 5:58 ` Christopher Faylor
2013-01-20 22:09 ` Tom Honermann
2013-01-23 3:20 ` Tom Honermann
2013-01-23 5:27 ` Christopher Faylor
2013-01-23 18:18 ` Tom Honermann
2013-01-23 18:35 ` Christopher Faylor
2013-01-24 4:12 ` Tom Honermann
2013-01-16 19:14 ` Christopher Faylor
2013-01-16 20:24 ` Tom Honermann
2012-12-21 20:01 ` Intermittent failures retrieving process exit codes Tom Honermann
2013-11-14 4:02 ` Tom Honermann
2013-11-14 9:20 ` Corinna Vinschen
2013-11-14 15:21 ` Tom Honermann
2013-11-15 18:53 ` Denis Excoffier
2013-11-15 19:21 ` Christopher Faylor
2013-11-17 13:30 ` Denis Excoffier
2013-11-15 22:15 ` Tom Honermann
2013-11-25 19:59 ` Lasse Collin
2013-11-25 23:12 ` Antivirus strikes back (probably) (Was: Intermittent failures retrieving process exit codes) Denis Excoffier
2013-11-26 21:09 ` Denis Excoffier
2013-11-26 23:36 ` Christopher Faylor
2013-11-26 21:09 ` Denis Excoffier
2013-12-01 13:24 ` Lasse Collin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130101053606.GB18911@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).