From: Yao Qi <yao@codesourcery.com>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix error when gdb connect to a stub that tracepoint is running[0/2]
Date: Tue, 31 Jan 2012 08:22:00 -0000 [thread overview]
Message-ID: <4F27A3DC.4010502@codesourcery.com> (raw)
In-Reply-To: <4F274C2C.7090107@mentor.com>
On 01/31/2012 10:04 AM, Hui Zhu wrote:
> (gdb) info tracepoints
> Num Type Disp Enb Address What
> 1 tracepoint keep y 0x0000000000400557 in main at 1.c:15
> collect $reg
> (gdb) set disconnected-tracing on
> (gdb) tstart
> (gdb) disconnect
> Trace is running and will continue after detach; detach anyway? (y or n) y
> Ending remote debugging.
> (gdb) target remote localhost:1234
> Remote debugging using localhost:1234
> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> Error in re-setting breakpoint 1: Target returns error code '01'.
> Target returns error code '01'.
> (gdb) disconnect
> You can't do that when your target is `exec'
> (gdb) quit
> gdb ./a.out
> (gdb) target remote localhost:1234
> Remote debugging using localhost:1234
> Reading symbols from /lib64/ld-linux-x86-64.so.2...(no debugging symbols
> found)...done.
> Loaded symbols for /lib64/ld-linux-x86-64.so.2
> 0x00007ffff7ddcaf0 in ?? () from /lib64/ld-linux-x86-64.so.2
> Trace is already running on the target.
> Tracepoint 1 at 0x400557: file 1.c, line 15.
> Target returns error code '01'.
>
Yes, this is a bug. It is better if we can convert these steps into a
.exp test case :).
--
Yao (é½å°§)
prev parent reply other threads:[~2012-01-31 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 2:05 Hui Zhu
2012-01-31 8:22 ` Yao Qi [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=4F27A3DC.4010502@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.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