From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org,
Joel Brobecker <brobecker@adacore.com>,
'Pedro Alves' <pedro@codesourcery.com>,
Pierre Muller <muller@ics.u-strasbg.fr>
Subject: Re: [RFC] win32-nat.c 'set new-console' and interruption
Date: Tue, 24 Jun 2008 06:33:00 -0000 [thread overview]
Message-ID: <20080624011456.GB13397@ednor.casa.cgf.cx> (raw)
In-Reply-To: <20080623195153.GA3746@adacore.com>
On Mon, Jun 23, 2008 at 03:51:53PM -0400, Joel Brobecker wrote:
>> I find it cleaner with signal SIGINT, but it's true that the other
>> option is simpler and not that different!
>
>I think most people would expect to see SIGINT. Also, seeing a SIGINT
>would make it consistent with what the user would see if the console
>was shared.
>
>> Christopher, should I just remove the ctrl_break_sent variable and
>> let GDB use SIGTRAP signal?
>
>So, I would personally prefered if we kept the SIGTRAP to SIGINT
>translation... Just my 2 cents.
I think that makes 4 cents. A SIGTRAP would be confusing.
I haven't looked at the patch yet, however.
cgf
next prev parent reply other threads:[~2008-06-24 1:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-21 17:05 Pierre Muller
2008-06-21 18:37 ` Christopher Faylor
2008-06-22 3:17 ` Daniel Jacobowitz
2008-06-22 3:18 ` Corinna Vinschen
2008-06-23 1:04 ` Christopher Faylor
2008-06-23 1:10 ` Corinna Vinschen
2008-06-23 7:40 ` Pierre Muller
2008-06-23 12:00 ` Christopher Faylor
2008-06-23 16:05 ` Pierre Muller
2008-06-23 17:00 ` Pedro Alves
2008-06-23 17:25 ` Pierre Muller
2008-06-23 18:03 ` Christopher Faylor
2008-06-23 19:24 ` Pedro Alves
2008-06-23 20:33 ` Pierre Muller
2008-06-23 21:06 ` Joel Brobecker
2008-06-24 6:33 ` Christopher Faylor [this message]
2008-06-24 13:36 ` [RFC-v3] " Pierre Muller
2008-06-24 2:33 ` [RFC] " Christopher Faylor
2008-06-24 13:54 ` Pedro Alves
2008-06-24 18:29 ` Christopher Faylor
2008-06-22 9:00 ` Christopher Faylor
2008-06-23 8:52 ` [RFC v2] " Pierre Muller
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=20080624011456.GB13397@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=muller@ics.u-strasbg.fr \
--cc=pedro@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