From: Stan Shebs <stanshebs@earthlink.net>
To: gdb-patches@sourceware.org
Subject: Re: [PATCH]tracepoint.c: Add conditionals num to find_matching_tracepoint
Date: Mon, 08 Aug 2011 23:02:00 -0000 [thread overview]
Message-ID: <4E406AE9.100@earthlink.net> (raw)
In-Reply-To: <CANFwon33P3x45wVo-37q8Z4J-sxyM7P3rLfx7QmbdzxQna-ohw@mail.gmail.com>
On 8/7/11 9:28 AM, Hui Zhu wrote:
> Hi,
>
> I found that when I set some tracepoint to a same address, and use
> tsave. And use "target tfile " to open it. It will only one
> tracepoint available.
> And output some words like:
> Created tracepoint 1 for target's tracepoint 1 at 0x40050a.
> Assuming tracepoint 1 is same as target's tracepoint 2 at 0x40050a.
> Assuming tracepoint 1 is same as target's tracepoint 3 at 0x40050a.
>
> This is because find_matching_tracepoint didn't check the num.
The number is exactly the one property that tracepoint upload must never
consider when looking for matching tracepoints, since the numbers vary
depending on what the user has been doing during the current GDB
session. Addressing the FIXME will help the multiple-tracepoint case,
although it's kind of messy.
There is another useful heuristic that would be easy to add, which is to
exclude matching on a tracepoint that has already been uploaded. Having
created tracepoint 1 from the uploaded info, it's never going to be the
case that uploaded tracepoints 2 and 3 are the same as 1. It might be
as simple as testing number_on_target, but beware that it might be
nonzero due to other trace runs or some such.
Stan
stan@codesourcery.com
>
> And I think the tracepoint have the same address is really helpful for
> user. Because we can set different condition to make tracepoint more
> powerful.
> So I make following patch.
>
> Please help me review it.
>
> Thanks,
> Hui
>
>
> 2011-08-08 Hui Zhu<teawater@gmail.com>
>
> * tracepoint.c (find_matching_tracepoint): Add number check.
next prev parent reply other threads:[~2011-08-08 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-07 16:30 Hui Zhu
2011-08-08 23:02 ` Stan Shebs [this message]
2011-08-14 13:41 ` Hui Zhu
2011-08-16 9:28 ` Hui Zhu
2011-08-23 8:53 ` Hui Zhu
2011-08-23 23:24 ` Stan Shebs
2011-08-24 9:30 ` Hui Zhu
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=4E406AE9.100@earthlink.net \
--to=stanshebs@earthlink.net \
--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