From: Pedro Alves <palves@redhat.com>
To: Andrew Burgess <andrew.burgess@embecosm.com>,
Alan Hayward <Alan.Hayward@arm.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
nd <nd@arm.com>
Subject: Re: [PATCH] Supress SIGTTOU when handling errors
Date: Thu, 23 May 2019 20:35:00 -0000 [thread overview]
Message-ID: <4adc2dd1-4b5b-f650-dad2-7ddf1433ab85@redhat.com> (raw)
In-Reply-To: <20190520091157.GC2568@embecosm.com>
On 5/20/19 10:11 AM, Andrew Burgess wrote:
> I share your concern, but...
>
> If you check the comment on 'child_terminal_ours_for_output' you'll
> see a little note left from before Pedro's commit e671cd59d74cec9f
> which says:
>
> /* Put some of our terminal settings into effect,
> enough to get proper results from our output,
> but do not change into or out of RAW mode
> so that no input is discarded.
>
> After doing this, either terminal_ours or terminal_inferior
> should be called to get back to a normal state of affairs.
>
> This next bit is interesting....
>
> N.B. The implementation is (currently) no different than
> child_terminal_ours. See child_terminal_ours_1. */
>
> void
> child_terminal_ours_for_output (struct target_ops *self)
> {
> child_terminal_ours_1 (1);
> }
Yeah. Whooops, I meant to fix that comment, clearly I forgot...
>
> So, until Pedro's change 'ours ()' and 'ours_for_output ()' were the
> same. Now that doesn't mean we should go back, but I think it means
> I'd be willing to consider it (hence why I originally came our against
> it, then changed my mind).
>
Thanks,
Pedro Alves
prev parent reply other threads:[~2019-05-23 20:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 15:51 Alan Hayward
2019-05-16 18:06 ` Andrew Burgess
2019-05-16 18:30 ` Andrew Burgess
2019-05-23 20:33 ` Pedro Alves
2019-05-17 12:47 ` Alan Hayward
2019-05-18 9:10 ` Andrew Burgess
2019-05-23 20:32 ` Pedro Alves
2019-05-24 8:54 ` Alan Hayward
[not found] ` <7483f478-44d2-b2ce-b0cb-3e984054305a@redhat.com>
2019-05-24 12:36 ` Alan Hayward
2019-05-24 13:15 ` Pedro Alves
2019-05-26 22:43 ` Andrew Burgess
2019-05-27 18:03 ` Pedro Alves
2019-05-28 9:39 ` Alan Hayward
2019-08-02 16:05 ` [8.3 backport] " Tom de Vries
2019-08-05 10:59 ` Alan Hayward
2019-08-05 17:33 ` Tom Tromey
2019-05-18 13:42 ` [PATCH] " Andreas Schwab
2019-05-19 22:06 ` Andrew Burgess
2019-05-20 8:44 ` Alan Hayward
[not found] ` <20190520091157.GC2568@embecosm.com>
2019-05-20 9:49 ` Pedro Alves
2019-05-23 20:35 ` Pedro Alves [this message]
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=4adc2dd1-4b5b-f650-dad2-7ddf1433ab85@redhat.com \
--to=palves@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=andrew.burgess@embecosm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=schwab@linux-m68k.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