Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: John Pye <john.pye@anu.edu.au>
Cc: gdb@sourceware.org
Subject: Re: usability: exiting from GDB
Date: Mon, 27 Nov 2006 13:42:00 -0000	[thread overview]
Message-ID: <uirh1ypj9.fsf@gnu.org> (raw)
In-Reply-To: <456A96F3.9060605@anu.edu.au> (message from John Pye on Mon, 27 	Nov 2006 18:42:43 +1100)

> Date: Mon, 27 Nov 2006 18:42:43 +1100
> From: John Pye <john.pye@anu.edu.au>
> CC:  gdb@sourceware.org
> 
> About that 'ctrl-C' behaviour -- any reason why this couldn't be changed
> (perhaps to do with signal handlers or somesuch)?

I don't think signal handlers are the issue.  I think the main
problems with this are: (1) there might be asynchronous commands
running even though you are sitting at the GDB prompt, and (2) due to
relatively slow human reaction times, you could hit Ctrl-C to
interrupt a command, but when that Ctrl-C gets to GDB the command
could already be done, which will dump you out of GDB.

But maybe treating Ctrl-C as q (with query) would be okay, I don't
know.


  reply	other threads:[~2006-11-27 13:42 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-27  5:38 John Pye
2006-11-27  6:50 ` Eli Zaretskii
2006-11-27  7:43   ` John Pye
2006-11-27 13:42     ` Eli Zaretskii [this message]
2006-11-27 13:51 ` Daniel Jacobowitz
2006-11-27 14:46 ` Andrew STUBBS
2006-11-29  3:27   ` John Pye
2006-11-29  4:50     ` Daniel Jacobowitz
2006-11-29  5:04     ` Joel Brobecker
2006-11-29  7:16       ` John Pye
2006-11-29 13:38         ` Daniel Jacobowitz
2006-11-29 14:12           ` Bob Rossi
2006-11-30  4:01             ` John Pye
2006-11-30  8:32               ` Brian Dessent
2006-11-30 11:58                 ` John Pye
2006-11-30 12:34                   ` Andrew STUBBS
2006-11-30  3:59           ` John Pye
2006-11-30 10:10             ` Andrew STUBBS
2006-11-30 11:51               ` John Pye
2006-11-30 21:49             ` Michael Snyder

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=uirh1ypj9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=john.pye@anu.edu.au \
    /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