From: John Pye <john.pye@anu.edu.au>
To: gdb@sourceware.org
Subject: Re: usability: exiting from GDB
Date: Thu, 30 Nov 2006 11:58:00 -0000 [thread overview]
Message-ID: <456EC746.7070605@anu.edu.au> (raw)
In-Reply-To: <456E9721.8346C359@dessent.net>
Brian Dessent wrote:
> John Pye wrote:
>
>
>> Note the vital difference here: bash never asks for confirmation on ctrl-D.
>>
> Did you really read the existing replies in this thread?
>
I was wrong here -- it does *sometimes* ask confirmation, as you've
pointed out.
> Daniel Jacobowitz wrote:
>
>> I don't know about you, but my shell prints a warning message if I try
>> to C-d while there are background jobs running. GDB's behaving
>> exactly the same :-)
>>
I did try this, but not with a suitable examples, perhaps. For example,
I was thinking of:
kompare &
ctrl-D
Also note
su
wget http://example.com/bigfile.iso &
ctrl-D
There is no confirmation request in these case, although I'm not
completely confident on drawing the distinction between these and the
'cat &' case that was given.
As the programs that I tend to be working on are often like this, I
hadn't really notices the 'stopped jobs' warning.
Cheers
JP
next prev parent reply other threads:[~2006-11-30 11:58 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
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 [this message]
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=456EC746.7070605@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