From: Eli Zaretskii <eliz@gnu.org>
To: "Dave Korn" <dave.korn@artimi.com>
Cc: jimb@codesourcery.com, Roland.Puntaier@br-automation.com,
gdb@sourceware.org
Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C
Date: Wed, 22 Aug 2007 19:17:00 -0000 [thread overview]
Message-ID: <u8x83wf9b.fsf@gnu.org> (raw)
In-Reply-To: <009a01c7e4a4$fdd913e0$2e08a8c0@CAM.ARTIMI.COM> (dave.korn@artimi.com)
> From: "Dave Korn" <dave.korn@artimi.com>
> Cc: <Roland.Puntaier@br-automation.com>,
> <gdb@sourceware.org>
> Date: Wed, 22 Aug 2007 11:12:48 +0100
>
> > Maybe I'm simply unaware of some subtle issues, but I don't know of
> > any situation where this cannot be done safely. In particular, the
> > code I wrote for GNU Make works since the release of Make 3.81, and I
> > have yet to see any problems with interrupting a running Make, or hear
> > a single complaint or bug report related to C-c.
>
> I'd be curious to take a look at that, can you point me at the right part of
> the sources?
Sure.
job.c:reap_children (search for "GetCurrentThread") is where I record
the thread ID of the main thread. command.c:fatal_error_signal is
where the main thread ID is used to stop the main thread as soon as we
enter the signal handler.
Let me know if you find any bugs ;-)
next prev parent reply other threads:[~2007-08-22 19:17 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 [this message]
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
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=u8x83wf9b.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Roland.Puntaier@br-automation.com \
--cc=dave.korn@artimi.com \
--cc=gdb@sourceware.org \
--cc=jimb@codesourcery.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