From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] Check trace data from trace file
Date: Tue, 26 Feb 2013 18:44:00 -0000 [thread overview]
Message-ID: <512D0297.5010703@redhat.com> (raw)
In-Reply-To: <512AD5CA.50606@codesourcery.com>
On 02/25/2013 03:08 AM, Yao Qi wrote:
> Here is the same patch with spaces ignored. It is easier to read.
> Note that I modified a matched pattern "PC register is not
> available" for tfile target, as the regcache is not available when
> switch to tfind mode (no regcache has been read out of 'R' block yet).
Hmmm. Not sure. Shouldn't something have caught that exception? IOW,
could that be a bug?
I'm having difficulty figuring it out, because when I run the test
I don't see that output anywhere in the gdb.log:
(gdb) printf "x %d x\n", $tracepoint
x 2 x
(gdb) PASS: gdb.trace/report.exp: tfile: 9.1: find frame for TP 2
tdump
Data collected at tracepoint 2, trace frame 0:
(gdb) PASS: gdb.trace/report.exp: tfile: 9.1: tdump, nothing collected
I wonder what's different in our environments.
>
> # Nothing was collected at tdp1, so this tdump should be empty.
> gdb_test "tdump" \
> - "Data collected at tracepoint $tdp1, trace frame $decimal:" \
> + "Data collected at tracepoint $tdp1, trace frame $decimal:\(\|\\r\\nPC register is not available\)" \
> "9.1: tdump, nothing collected"
--
Pedro Alves
next prev parent reply other threads:[~2013-02-26 18:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 2:58 Yao Qi
2013-02-25 2:58 ` [PATCH 2/2] Find the next matched trace file in 'tfile target' Yao Qi
2013-02-26 19:53 ` Pedro Alves
2013-02-27 1:37 ` Yao Qi
2013-02-25 3:10 ` [PATCH 1/2] Check trace data from trace file Yao Qi
2013-02-26 18:44 ` Pedro Alves [this message]
2013-02-26 18:57 ` Pedro Alves
2013-02-27 1:54 ` Yao Qi
2013-02-27 15:23 ` Pedro Alves
2013-02-28 1:14 ` Yao Qi
2013-02-25 12:03 ` Abid, Hafiz
2013-02-25 14:10 ` 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=512D0297.5010703@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