Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: John Baldwin <jhb@freebsd.org>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Fix PR gdb/18653: gdb disturbs inferior's inherited signal dispositions
Date: Mon, 22 Aug 2016 14:34:00 -0000	[thread overview]
Message-ID: <e7d765fc-d4cb-984f-1fe4-b9f01b6e22d9@redhat.com> (raw)
In-Reply-To: <864m6cdgju.fsf@gmail.com>

On 08/22/2016 03:28 PM, Yao Qi wrote:

> How about the patch below?  It follows the way we fix the problem of
> this kind in mi-traceframe-changed.exp and tfile.exp.
> 
> How about the patch below?  It should go to master and 7.12 branch.

LGTM.

Thanks,
Pedro Alves


  reply	other threads:[~2016-08-22 14:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 17:37 [PATCH] " Pedro Alves
2016-08-05  0:08 ` John Baldwin
2016-08-05  1:04   ` Pedro Alves
2016-08-05 10:57     ` [PATCH v2] " Pedro Alves
2016-08-08 17:28       ` John Baldwin
2016-08-12  8:21       ` Yao Qi
2016-08-12  9:08         ` Pedro Alves
2016-08-22 14:28       ` Yao Qi
2016-08-22 14:34         ` Pedro Alves [this message]
2016-08-23 13:20           ` Yao Qi

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=e7d765fc-d4cb-984f-1fe4-b9f01b6e22d9@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jhb@freebsd.org \
    --cc=qiyaoltc@gmail.com \
    /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