From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: <palves@redhat.com>
Subject: [PATCH 0/3] Tweak server-kill.exp for remote target
Date: Wed, 08 Oct 2014 06:32:00 -0000 [thread overview]
Message-ID: <1412749679-27076-1-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <543404EF.4010306@redhat.com>
Pedro Alves <palves@redhat.com> writes:
> gdbserver will be the parent of the tested process. So how about
> tweaking the test program to do:
>
> int server_pid;
>
> int main ()
> {
> server_pid = getppid ();
> }
>
> and then simply read "server_pid" out of the inferior ?
That is a good idea! Patch 2/3 is about this. Patch 1/3 is a clean
up. Patch 3/3 is to fix a fail we've seen on target doesn't support
tracepoint.
*** BLURB HERE ***
Yao Qi (3):
Clean up server-kill.exp
Get GDBserver pid on remote target
Use command "monitor set debug 0" to check the connection
gdb/testsuite/gdb.server/server-kill.c | 10 +++++++++-
gdb/testsuite/gdb.server/server-kill.exp | 23 +++++++++++++++++------
2 files changed, 26 insertions(+), 7 deletions(-)
--
1.9.3
next prev parent reply other threads:[~2014-10-08 6:32 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 " Yao Qi
2014-10-07 13:55 ` Yao Qi
2014-10-07 15:21 ` Pedro Alves
2014-10-08 6:32 ` Yao Qi [this message]
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
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=1412749679-27076-1-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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