From: Pedro Alves <palves@redhat.com>
To: "Abid, Hafiz" <hafiz_abid@mentor.com>
Cc: Yao Qi <yao@codesourcery.com>,
gdb-patches@sourceware.org, stan@codesourcery.com,
eliz@gnu.org
Subject: Re: [patch] Change trace buffer size(v5)
Date: Thu, 02 May 2013 17:31:00 -0000 [thread overview]
Message-ID: <5182A2F8.2050900@redhat.com> (raw)
In-Reply-To: <1362755693.30327.1@abidh-ubunto1104>
Hi!
Unfortunately, I just noticed that this broke "tstart" if a
trace run is already running:
(gdb) tstart
A trace is running already. Start a new run? (y or n) y
Sending packet: $QTinit#59...Packet received: OK
Sending packet: $QTDP:3:0000000000410296:E:0:0#49...Packet received: OK
Sending packet: $QTDPsrc:3:410296:at:0:4:6d61696e#8a...Packet received: OK
Sending packet: $QTDV:1:0000000000000000:1:74726163655f74696d657374616d70#4f...Packet received: OK
Sending packet: $:0000000000400200,000000000040021c:000000000040021c,000000000040023c:000000000040023c,0000000000400260:0000000000400260,00000000004002c0:00000000004002c0,0000000000400ff8:0000000000400ff8,000000000040149e:000000000040149e,00000000004015b8:00000000004015b8,0000000000401628:0000000000401628,0000000000401688:0000000000401688,0000000000402210:0000000000402210,000000000040221e:0000000000402220,00000000004029e0:00000000004029e0,000000000043a230:000000000043a230,000000000043a239:000000000043a240,000000000044cafd:000000000044cb00,000000000044e834:000000000044e838,00000000004560a4#ab...Packet received:
Sending packet: $QTDisconnected:0#e2...Packet received: OK
Sending packet: $QTBuffer:circular:0#f8...Packet received: OK
Sending packet: $QTBuffer:size:-1#8c...Packet received: E01
Target returns error code '01'.
(gdb)
Perhaps gdbserver's QTinit handling should be calling
stop_tracing?
--
Pedro Alves
next prev parent reply other threads:[~2013-05-02 17:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:13 [patch] Change trace buffer size Abid, Hafiz
2013-02-18 20:00 ` Eli Zaretskii
2013-02-19 2:53 ` Yao Qi
2013-02-27 16:55 ` Pedro Alves
2013-02-28 0:52 ` Yao Qi
2013-02-27 16:39 ` Pedro Alves
2013-03-01 17:07 ` [patch] Change trace buffer size(v2) Abid, Hafiz
2013-03-01 18:13 ` zinteger setshow commands broken Pedro Alves
2013-03-04 10:10 ` Abid, Hafiz
2013-03-04 10:16 ` Yao Qi
2013-03-04 10:28 ` Pedro Alves
2013-03-01 20:02 ` [patch] Change trace buffer size(v2) Pedro Alves
2013-03-04 19:03 ` [patch] Change trace buffer size(v3) Abid, Hafiz
2013-03-04 20:43 ` Pedro Alves
2013-03-05 14:12 ` [patch] Change trace buffer size(v4) Abid, Hafiz
2013-03-05 20:13 ` Pedro Alves
2013-03-08 11:30 ` [patch] Change trace buffer size(v5) Abid, Hafiz
2013-03-08 14:09 ` Eli Zaretskii
2013-03-08 14:27 ` Abid, Hafiz
2013-03-08 14:28 ` Pedro Alves
2013-03-08 14:52 ` Yao Qi
2013-03-08 15:15 ` Abid, Hafiz
2013-03-08 15:27 ` Yao Qi
2013-05-02 17:31 ` Pedro Alves [this message]
2013-05-03 11:38 ` Abid, Hafiz
2013-05-03 14:05 ` Pedro Alves
2013-05-03 15:08 ` Abid, Hafiz
2013-05-03 15:26 ` Pedro Alves
2013-03-09 2:06 ` Joel Brobecker
2013-03-09 8:27 ` Eli Zaretskii
2013-03-09 10:20 ` Abid, Hafiz
2013-03-09 10:39 ` Abid, Hafiz
2013-03-09 11:11 ` Eli Zaretskii
2013-03-09 11:07 ` Eli Zaretskii
2013-03-11 18:33 ` Tom Tromey
2013-03-11 19:44 ` Eli Zaretskii
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=5182A2F8.2050900@redhat.com \
--to=palves@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=hafiz_abid@mentor.com \
--cc=stan@codesourcery.com \
--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