From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Roland.Puntaier@br-automation.com, gdb@sourceware.org
Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C
Date: Tue, 21 Aug 2007 03:22:00 -0000 [thread overview]
Message-ID: <uy7g5tvvo.fsf@gnu.org> (raw)
In-Reply-To: <20070820193128.GA17272@caradoc.them.org> (message from Daniel Jacobowitz on Mon, 20 Aug 2007 15:31:28 -0400)
> Date: Mon, 20 Aug 2007 15:31:28 -0400
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Roland.Puntaier@br-automation.com, gdb@sourceware.org
>
> On Mon, Aug 20, 2007 at 10:16:12PM +0300, Eli Zaretskii wrote:
> > The way to fix this is to make the signal handler stop the main thread
> > as the first thing it does. Then you have a Posix-compliant program
> > again. I did something similar for the MinGW port of GNU Make.
>
> Is there any way to force the other thread to longjmp? Otherwise,
> just stopping it isn't enough - you don't have the right stack.
longjmp should (theoretically) handle this allright. But if not, you
could raise a flag in the signal handler, then resume the main thread
and return, and the main thread could check the flag and longjmp.
prev parent reply other threads:[~2007-08-21 3:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 16:20 Roland Puntaier
2007-08-20 16:24 ` Daniel Jacobowitz
2007-08-20 19:16 ` Eli Zaretskii
2007-08-20 19:31 ` Daniel Jacobowitz
2007-08-21 2:56 ` Christopher Faylor
2007-08-21 17:42 ` Jim Blandy
2007-08-21 19:09 ` Eli Zaretskii
2007-08-21 23:47 ` Jim Blandy
2007-08-22 3:13 ` Eli Zaretskii
2007-08-22 10:13 ` Dave Korn
2007-08-22 19:17 ` Eli Zaretskii
2007-08-24 9:19 ` Roland Puntaier
2007-08-24 16:12 ` Roland Puntaier
2007-08-21 22:55 ` Christopher Faylor
2007-08-22 11:10 ` Roland Puntaier
2007-08-22 19:20 ` Eli Zaretskii
2007-08-23 2:49 ` 答复: (Rising Spam Alert)Re: " xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
2007-08-23 2:49 ` xchen
[not found] ` <NUTMEGt3HvoFOAmEaJs0000003d@mail.artimi.com>
2007-08-23 9:30 ` Dave Korn
2007-08-21 3:22 ` Eli Zaretskii [this message]
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=uy7g5tvvo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Roland.Puntaier@br-automation.com \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
/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