From: John Pye <john.pye@anu.edu.au>
To: gdb@sourceware.org
Subject: usability: exiting from GDB
Date: Mon, 27 Nov 2006 05:38:00 -0000 [thread overview]
Message-ID: <456A79B5.2020505@anu.edu.au> (raw)
Hi all
GDB is a great tool that efficiently does what it needs to do, and I use
it almost every day. But there's something about it that annoys be every
single time I use it. I wonder if this is something that other people
find, and if so, perhaps there's solution?
What I would like is that (a) the 'ctrl-C' behaviour from the gdb prompt
was changed so that instead of (I think uselessly) outputting 'Quit' and
bringing up another prompt line, it actually *did* quit GDB. Or,
alternatively, (b) that the following prompted could somehow be
persistently disabled: "The program is running. Exit anyway? (y or n)".
I often find that in exiting GDB, which requires ctrl-D to be pressed
twice, I press ctrl-D three times and end up also logging out of my
terminal program, which is annoying.
Another issue is that after exiting GDB via ctrl-D-ctrl-D, GDB doesn't
output a newline, which causes the following bash input line to be
messed up.
I realise that this is a long-winded email about a very minor issue.
Humour me?
Cheers
JP
next reply other threads:[~2006-11-27 5:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 5:38 John Pye [this message]
2006-11-27 6:50 ` Eli Zaretskii
2006-11-27 7:43 ` John Pye
2006-11-27 13:42 ` Eli Zaretskii
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=456A79B5.2020505@anu.edu.au \
--to=john.pye@anu.edu.au \
--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