From: "wenji dot huang at oracle dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/10015] Possible uninitialized variable use in sym.c
Date: Wed, 01 Apr 2009 01:46:00 -0000 [thread overview]
Message-ID: <20090401014609.27188.qmail@sourceware.org> (raw)
In-Reply-To: <20090330184343.10015.wcohen@redhat.com>
------- Additional Comments From wenji dot huang at oracle dot com 2009-04-01 01:46 -------
This part is copy code from kernel/kallsyms.c. The variables can't be used
but uninitialized. Seems gcc on rawhide doesn't understand it well. Anyway,
we can get by it through uninitialized_var.
diff --git a/runtime/sym.c b/runtime/sym.c
index 1d88a86..be05354 100644
--- a/runtime/sym.c
+++ b/runtime/sym.c
@@ -236,9 +236,9 @@ static int _stp_module_check(void)
static void _stp_symbol_print(unsigned long address)
{
- const char *modname;
+ const char *uninitialized_var(modname);
const char *name;
- unsigned long offset, size;
+ unsigned long uninitialized_var(offset), uninitialized_var(size);
name = _stp_kallsyms_lookup(address, &size, &offset, &modname, NULL);
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10015
------- 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-04-01 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 21:27 [Bug runtime/10015] New: " wcohen at redhat dot com
2009-03-30 21:28 ` [Bug runtime/10015] " wcohen at redhat dot com
2009-03-30 21:29 ` wcohen at redhat dot com
2009-04-01 1:46 ` wenji dot huang at oracle dot com [this message]
2009-11-13 9:19 ` wenji dot huang at oracle dot com
2009-11-13 12:38 ` 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=20090401014609.27188.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).