From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/5076] detect both inlined and non-inlined function instances
Date: Wed, 11 Jun 2008 15:03:00 -0000 [thread overview]
Message-ID: <20080611142517.31876.qmail@sourceware.org> (raw)
In-Reply-To: <20070928173926.5076.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-06-11 14:25 -------
Maybe the solution to this one is to accept (and confirm) that .function.call and
.function.return probes match up, rather than .function and .function.return.
Any extras (inlined instances) would not show up under .call, so they should not
need special treatment like warnings/etc. for .return probes.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=5076
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2008-06-11 14:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 1:19 [Bug translator/5076] New: " fche at redhat dot com
2008-06-11 15:03 ` fche at redhat dot com [this message]
2010-09-27 14:23 ` [Bug translator/5076] " fche at redhat dot com
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=20080611142517.31876.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).