From: Andreas Schwab <schwab@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "dpc\@ucore.info" <dpc@ucore.info>,
Tristan Gingold <gingold@adacore.com>,
Pedro Alves <pedro@codesourcery.com>,
gdb@sourceware.org, Mike Frysinger <vapier@gentoo.org>
Subject: Re: gdb + remote qemu, Ctrl-C does not work
Date: Wed, 02 Mar 2011 16:12:00 -0000 [thread overview]
Message-ID: <m3aahdfqnu.fsf@redhat.com> (raw)
In-Reply-To: <20110302150359.GB2513@adacore.com> (Joel Brobecker's message of "Wed, 2 Mar 2011 19:03:59 +0400")
Joel Brobecker <brobecker@adacore.com> writes:
> That's only the case with interactive shells! In non-interactive
> shell sessions (typically a script), background process are still
> launched with the same process group as the parent script.
This is not about interactive vs. non-interactive, but a matter of job
control. You can enable/disable job control independent of whether the
shell is interactive.
Andreas.
--
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
"And now for something completely different."
next prev parent reply other threads:[~2011-03-02 16:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimvhnQs_4gTkaU_xfgjnm0G=Qkm-ZdzVYJ9nmfK@mail.gmail.com>
2011-03-01 14:48 ` dpc
2011-03-01 18:35 ` Mike Frysinger
2011-03-01 22:52 ` dpc
2011-03-01 23:50 ` Mike Frysinger
2011-03-02 7:29 ` dpc
2011-03-02 9:45 ` Pedro Alves
2011-03-02 12:29 ` dpc
2011-03-02 12:49 ` Pedro Alves
2011-03-02 13:07 ` Tristan Gingold
2011-03-02 14:17 ` Pedro Alves
2011-03-02 14:24 ` Tristan Gingold
2011-03-02 14:26 ` dpc
2011-03-02 15:04 ` Joel Brobecker
2011-03-02 16:12 ` Andreas Schwab [this message]
2011-03-02 10:12 ` Andreas Schwab
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=m3aahdfqnu.fsf@redhat.com \
--to=schwab@redhat.com \
--cc=brobecker@adacore.com \
--cc=dpc@ucore.info \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
--cc=pedro@codesourcery.com \
--cc=vapier@gentoo.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