From: Patrick Palka <patrick@parcs.ath.cx>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Patrick Palka <patrick@parcs.ath.cx>
Subject: Re: [PATCH] Call target_terminal_ours in quit_force
Date: Mon, 27 Jul 2015 16:12:00 -0000 [thread overview]
Message-ID: <CA+C-WL-wNHbKxg95yLtN6V9myY5iqXSWcwOkTmO5ZOjS=x3jnQ@mail.gmail.com> (raw)
In-Reply-To: <1438013299-1449-1-git-send-email-patrick@parcs.ath.cx>
On Mon, Jul 27, 2015 at 12:08 PM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> We should make sure our terminal settings are in effect before finally
> quitting GDB. Our terminal settings may not be in effect at this point
> if we are e.g. quitting due to a SIGTERM.
I should add, "quitting due to a SIGTERM while an inferior an inferior
is running in the foreground."
next prev parent reply other threads:[~2015-07-27 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 16:08 Patrick Palka
2015-07-27 16:12 ` Patrick Palka [this message]
2015-07-27 16:37 ` Andreas Schwab
2015-07-27 18:23 ` Pedro Alves
2015-07-27 18:49 ` Patrick Palka
2015-07-27 19:12 ` Patrick Palka
2015-07-28 10:41 ` Pedro Alves
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='CA+C-WL-wNHbKxg95yLtN6V9myY5iqXSWcwOkTmO5ZOjS=x3jnQ@mail.gmail.com' \
--to=patrick@parcs.ath.cx \
--cc=gdb-patches@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