From: "Mortimer, Andy" <Andy.Mortimer@software.aeat.com>
To: "'cygwin@sources.redhat.com'" <cygwin@sources.redhat.com>
Subject: RE: sig_send: wait for sig_complete event failed
Date: Mon, 02 Oct 2000 04:50:00 -0000 [thread overview]
Message-ID: <2E300728EEF9D3119D8000E018C1864F5E428C@gemini> (raw)
Chris Faylor writes:
> On Wed, Sep 20, 2000 at 11:23:55AM +0100, Mortimer, Andy wrote:
> >> >>On Fri, Sep 15, 2000 at 12:01:52PM +0100, Mortimer, Andy wrote:
> >> >>>1184486202 [sig] bash 28849 sig_send: wait for sig_complete
> >> >>> event failed, sig 11, rc 258, Win32 error 0
> >> >> [...]
> >> >As noted in another message, the latest snapshots didn't work for me,
> >> >but I've applied just the patch referred to here and it has indeed
> >> >stopped the hang. Thanks, Chris! Now, I'm just left with the problem
> >> >of bash segfaulting inside Cygwin's signal handling thread ... ;-)
> >
> >6100922E stack_info::init(unsigned long) exceptions.cc:226
> >6100922E stack_info::init(unsigned long) exceptions.cc:226
> >6100A2A3 interrupt_on_return(unsigned long, int, sigaction &, void *) exceptions.cc:663
> >6100A806 call_handler(int, sigaction &, void *) exceptions.cc:778
> >6100AF00 sig_handle(int) exceptions.cc:972
> >6103EE0E wait_sig(void *) sigproc.cc:1269
> >6100331A thread_stub(void *) debug.cc:91
> >77F04EE8 ?? ??:0
>
> I've added some more code to the snapshots in an attempt to work
> around this problem. I don't know if I was successful or not. It's
> hard to fix a problem when you can't duplicate it.
I know, and I appreciate your trying to fix it anyway! Unfortunately
I'm still unable to come up with a reproducible testcase -- the
most reliable failure I have is still once in every four or five times,
and deep inside a large shell script at that. :-(
I will try to test the new snapshot sooner rather than later; I had
a look just now, but the latest snapshot (2000-Sep-29) doesn't
seem to include anything "obvious". Is this the one I should try,
or will the changes be in the next snapshot build?
Thanks,
Andy
--
Andy Mortimer, CFX Software Development
andy.mortimer@aeat.com
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-10-02 4:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 4:50 Mortimer, Andy [this message]
2000-10-02 8:47 ` Chris Faylor
-- strict thread matches above, loose matches on Subject: below --
2001-12-31 1:15 paul
2000-10-05 2:51 Mortimer, Andy
2000-09-20 3:27 Mortimer, Andy
2000-09-30 10:17 ` Chris Faylor
2000-09-19 10:13 Mortimer, Andy
2000-09-19 10:41 ` Chris Faylor
2000-09-15 5:57 Mortimer, Andy
2000-09-15 5:10 Earnie Boyd
2000-09-15 4:04 Mortimer, Andy
2000-09-18 10:57 ` Chris Faylor
1998-11-24 21:59 sig_send(): " Eric Barton
1998-11-26 11:26 ` Victor Ott
1998-12-02 19:49 ` John Alvord
1998-12-19 8:33 ` John Alvord
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=2E300728EEF9D3119D8000E018C1864F5E428C@gemini \
--to=andy.mortimer@software.aeat.com \
--cc=cygwin@sources.redhat.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).