Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Attach discard_pending_stop_replies to observer inferior_exit
Date: Fri, 14 Dec 2012 13:48:00 -0000	[thread overview]
Message-ID: <50CB2E18.2090701@redhat.com> (raw)
In-Reply-To: <50CB29D2.4000205@codesourcery.com>

On 12/14/2012 01:29 PM, Yao Qi wrote:
> On 12/14/2012 05:53 PM, Pedro Alves wrote:
>> GDB can be learning about new processes it didn't know about yet
>> from some yet-unprocessed stop reply.  So if we only clear stop replies
>> specific to each inferior, we'd leave those behind.  But, we're closing
>> the remote target here.  We really want to discard everything.
> 
> I see, then I change 'discard_pending_stop_replies' a little that INF
> is NULL means discard everything.  This patch is tested on x86_64-linux
> with native and gdbserver.  OK?

OK.

Thanks,
-- 
Pedro Alves


      reply	other threads:[~2012-12-14 13:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-07  2:51 Yao Qi
2012-12-14  1:57 ` [ping]: " Yao Qi
2012-12-14  9:53 ` Pedro Alves
2012-12-14 13:30   ` Yao Qi
2012-12-14 13:48     ` 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=50CB2E18.2090701@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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