From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/1155] inline function parameters
Date: Tue, 12 Aug 2008 20:45:00 -0000 [thread overview]
Message-ID: <20080812204405.13903.qmail@sourceware.org> (raw)
In-Reply-To: <20050802201026.1155.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2008-08-12 20:44 -------
With aoliva's latest gcc var-tracking code, linux 2.6.27-rc2 was compilable,
runnable, and showed some promise with respect to inline function parameters.
For example, this started to work:
probe kernel.function("context_switch") {println($next)}
However, by printing "$$vars" instead, one can see that the other parameters
are not visible at that place. Setting a statement probe a few lines down
exposes $prev and a few more locals though, which is a good sign.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=1155
------- 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-08-12 20:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050802201026.1155.fche@redhat.com>
2006-02-13 17:34 ` [Bug translator/1155] inline functions fche at redhat dot com
2006-07-14 23:19 ` dwilder at us dot ibm dot com
2006-08-09 3:01 ` guanglei at cn dot ibm dot com
2006-12-04 16:23 ` jblunck at suse dot de
2006-12-11 1:30 ` pinskia at gcc dot gnu dot org
2006-12-11 17:19 ` fche at redhat dot com
2007-03-30 18:26 ` [Bug translator/1155] inline function parameters fche at redhat dot com
2007-05-02 12:18 ` Packaging systemtap John Liang
2007-05-02 13:37 ` Eugene Teo
2007-05-02 13:43 ` Martin Hunt
2007-05-02 18:42 ` Frank Ch. Eigler
2007-05-03 14:10 ` John Liang
2007-05-15 21:08 ` [Bug translator/1155] inline function parameters wcohen at redhat dot com
2007-05-16 15:56 ` wcohen at redhat dot com
2008-01-02 22:16 ` mhiramat at redhat dot com
2008-01-09 16:26 ` mhiramat at redhat dot com
2008-08-12 20:45 ` fche at redhat dot com [this message]
2008-09-16 15:38 ` mjw at redhat dot com
2008-11-13 8:36 ` srikar at linux dot vnet dot ibm dot com
2010-05-13 18:22 ` 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=20080812204405.13903.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).