Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: John Pye <john.pye@anu.edu.au>
Cc: gdb@sourceware.org
Subject: Re: usability: exiting from GDB
Date: Thu, 30 Nov 2006 12:34:00 -0000	[thread overview]
Message-ID: <456ECFC4.2060204@st.com> (raw)
In-Reply-To: <456EC746.7070605@anu.edu.au>

John Pye wrote:
> 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.

The examples you give are not stopped jobs. They are background jobs.

'cat &' starts cat and then tries to put it in the background, but it 
doesn't like that so it stops (I'm not sure what mechanism stops it). 
Other programs are less fussy - they will run in the back ground quite 
happily. When the shell quits, they continue running, still in the 
background.

Try this instead:

bash$ kompare
<Ctrl-Z>
bash$ <Ctrl-D>

The Ctrl-Z stops (pauses) the foreground job. By this mechanism you can 
reproduce the effect with any program that does not have special SIGSTOP 
handling.

Sorry if I sent you a slightly less than general case example.

Andrew


  reply	other threads:[~2006-11-30 12:34 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
2006-11-30 12:34                   ` Andrew STUBBS [this message]
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=456ECFC4.2060204@st.com \
    --to=andrew.stubbs@st.com \
    --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