From: "wenji dot huang at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/6979] using $$parms under uprobe probes might result in a uninitialized variable access.
Date: Wed, 04 Feb 2009 11:34:00 -0000 [thread overview]
Message-ID: <20090204031055.9437.qmail@sourceware.org> (raw)
In-Reply-To: <20081024082201.6979.srikar@linux.vnet.ibm.com>
------- Additional Comments From wenji dot huang at oracle dot com 2009-02-04 03:10 -------
(In reply to comment #5)
> I added some print code to loc2c, before
> 237 switch (expr[i].atom)
> 238 {
> found there was one kind of dwarf_location_atom happened, DW_OP_breg5 = 0x75
> but not processed by loc2c. Maybe this will the culprit.
Sorry, DW_OP_breg5 is covered. Please ignore the comment.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=6979
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-02-04 3:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-24 8:23 [Bug translator/6979] New: " srikar at linux dot vnet dot ibm dot com
2009-02-03 6:21 ` [Bug translator/6979] " wenji dot huang at oracle dot com
2009-02-03 14:07 ` wenji dot huang at oracle dot com
2009-02-03 19:42 ` fche at redhat dot com
2009-02-04 3:11 ` wenji dot huang at oracle dot com
2009-02-04 5:56 ` wenji dot huang at oracle dot com
2009-02-04 11:34 ` wenji dot huang at oracle dot com [this message]
2009-02-04 17:08 ` fche at redhat dot com
2009-02-05 14:55 ` wenji dot huang at oracle dot com
2009-02-05 21:05 ` fche at redhat dot com
2009-02-20 14:24 ` fche at redhat dot com
2009-06-11 12:31 ` srikar at linux dot vnet dot ibm dot com
2009-11-11 14:35 ` fche at redhat dot com
2009-11-11 20:21 ` roland at gnu dot org
2009-11-18 17:32 ` fche at redhat dot com
2009-11-18 18:29 ` [Bug translator/6979] loc2c code generation error, uninitialized variable access, mishandling of multiple-piece $target vars 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=20090204031055.9437.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).