From: "Abid, Hafiz" <hafiz_abid@mentor.com>
To: <gdb-patches@sourceware.org>
Subject: Re: [patch] circ.exp
Date: Thu, 11 Apr 2013 22:59:00 -0000 [thread overview]
Message-ID: <1365686537.9625.1@abidh-ubunto1104> (raw)
In-Reply-To: <1363803795.2570.4@abidh-ubunto1104> (from hafiz_abid@mentor.com on Wed Mar 20 18:23:15 2013)
Ping. Original post at
http://sourceware.org/ml/gdb-patches/2013-03/msg00760.html
On 20/03/13 18:23:15, Abid, Hafiz wrote:
> Hi All,
> This is patch to refactor circ.exp. I noticed that it was quitting
> early as gdb_target_supports_trace was failing. There were some
> other issues too. After the changes, it is running to completion.
> How does it look?
>
> One test is failing that probably shows a defect. Following session,
> which is edited for clarity, shows the problem. When there is not
> enough buffer left (3rd frame onward), target does not stop the
> trace. It continues but only uses 6 bytes for the frame.
>
> (gdb) set trace-buffer-size 200
> (gdb) tstart
> (gdb) c
> ...
> (gdb) tstatus
> Collected 1 trace frames.
> Trace buffer has 131 bytes of 200 bytes free (34% full).
> ...
> (gdb) c
> ...
> (gdb) tstatus
> Collected 2 trace frames.
> Trace buffer has 62 bytes of 200 bytes free (69% full).
> ...
> (gdb) c
> ...
> (gdb) tstatus
> Trace is running on the target.
> Collected 3 trace frames.
> Trace buffer has 56 bytes of 200 bytes free (72% full).
> ...
> (gdb) c
> ...
> (gdb) tstatus
> Collected 4 trace frames.
> Trace buffer has 50 bytes of 200 bytes free (75% full).
> ...
> (gdb) c
> ...
> (gdb) tstatus
> Collected 5 trace frames.
> Trace buffer has 44 bytes of 200 bytes free (78% full).
> ...
> (gdb) tstop
> (gdb) tfind start
> Found trace frame 0, tracepoint 11
> #0 func0 () at ../.././../git/gdb/testsuite/gdb.trace/circ.c:11
> 11 }
> (gdb) p testload
> $4 = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13}
> (gdb) tfind 4
> Found trace frame 4, tracepoint 5
> 27 }
> (gdb) p testload
> $5 = {<unavailable> <repeats 13 times>}
>
>
> Regards,
> Abid
>
> gdb/testsuite:
>
> 2013-03-20 Hafiz Abid Qadeer <abidh@codesourcery.com>
>
> * gdb.trace/circ.exp: (run_trace_experiment): Test
> setup_tracepoints and 'break end' in it.
> (trace_buffer_normal): Refactor it to...
> (support_trace_packet). ..this.
> (gdb_trace_circular_tests): Remove. Move tests to...
> (top level): ... here. Call 'runto_main' before checking for
> trace support. Call 'support_trace_packets' to check the
> support for QTBuffer:size and QTBuffer:circular.
next prev parent reply other threads:[~2013-04-11 13:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 18:26 Abid, Hafiz
2013-04-11 22:59 ` Abid, Hafiz [this message]
2013-04-16 7:52 ` Pedro Alves
2013-04-16 20:53 ` Abid, Hafiz
2013-04-17 20:33 ` Pedro Alves
2013-04-17 20:54 ` Abid, Hafiz
2013-04-18 10:30 ` Pedro Alves
2013-04-18 11:09 ` Pedro Alves
2013-12-13 17:49 ` [PATCH] "tfind" across unavailable-stack frames Pedro Alves
2013-12-14 6:23 ` Yao Qi
2013-12-16 16:19 ` Pedro Alves
2013-12-17 9:04 ` Yao Qi
2013-12-17 10:09 ` Pedro Alves
2013-12-17 12:39 ` Yao Qi
2013-12-17 20:55 ` Pedro Alves
2013-12-16 8:40 ` Metzger, Markus T
2013-12-16 16:25 ` Pedro Alves
2013-12-16 16:42 ` [PATCH v2] " Pedro Alves
2013-04-19 14:27 ` [patch] circ.exp Abid, Hafiz
2013-04-19 14:28 ` Pedro Alves
2013-05-08 10:12 ` Abid, Hafiz
2013-05-08 15:13 ` Pedro Alves
2013-05-08 16:18 ` Abid, Hafiz
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=1365686537.9625.1@abidh-ubunto1104 \
--to=hafiz_abid@mentor.com \
--cc=gdb-patches@sourceware.org \
/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