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 3/3] Use command "monitor set debug 0" to check the connection
Date: Fri, 10 Oct 2014 13:57:00 -0000	[thread overview]
Message-ID: <5437E5B9.9000804@redhat.com> (raw)
In-Reply-To: <87lhooox25.fsf@codesourcery.com>

On 10/10/2014 02:48 PM, Yao Qi wrote:
> Pedro Alves <palves@redhat.com> writes:
>> I know that the test originally didn't use "tstatus",
>> but it's really the packet we should be testing for exercising
>> that remote_get_trace_status's exception swallowing code,
>> which was very much related to the original bug this test covered,
>> see:
>>
>>   https://sourceware.org/bugzilla/show_bug.cgi?id=15275
>>
>>   https://sourceware.org/ml/gdb-patches/2013-03/msg00691.html
> 
> Thanks for the information.  I remember the first half of the
> story, but forget the second half.  How about the patch below?

Looks good.

Thanks,
Pedro Alves


  reply	other threads:[~2014-10-10 13:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-30 13:15 [PATCH] Skip server-kill.exp on remote target Yao Qi
2014-10-07 13:55 ` Yao Qi
2014-10-07 15:21 ` Pedro Alves
2014-10-08  6:32   ` [PATCH 0/3] Tweak server-kill.exp for " Yao Qi
2014-10-08  6:32     ` [PATCH 1/3] Clean up server-kill.exp Yao Qi
2014-10-08 13:48       ` Pedro Alves
2014-10-08  6:32     ` [PATCH 3/3] Use command "monitor set debug 0" to check the connection Yao Qi
2014-10-08 14:19       ` Pedro Alves
2014-10-09  3:05         ` Yao Qi
2014-10-10  9:38           ` Pedro Alves
2014-10-10 13:52             ` Yao Qi
2014-10-10 13:57               ` Pedro Alves [this message]
2014-10-08  6:32     ` [PATCH 2/3] Get GDBserver pid on remote target Yao Qi
2014-10-08 14:07       ` Pedro Alves
2014-10-11  3:20     ` [PATCH 0/3] Tweak server-kill.exp for " 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=5437E5B9.9000804@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