public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
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: Tue, 03 Feb 2009 06:21:00 -0000	[thread overview]
Message-ID: <20090203053644.20035.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-03 05:36 -------
Reproduced it using testsuite/systemtap.examples/general/para-callgraph.stp

$sudo stap -vv para-callgraph.stp 'kernel.function("*@fs/proc*.c")'
'kernel.function("sys_read")'
...
Pass 3: translated to C into
"/tmp/stapI6MOvi/stap_6d7c9a6d948642fb62a56ab0e7db8c2b_133065.c" in
1840usr/2400sys/4935real ms.
Running make -C "/lib/modules/2.6.29-rc3/build" M="/tmp/stapI6MOvi" modules
>/dev/null
cc1: warnings being treated as errors
/tmp/stapI6MOvi/stap_6d7c9a6d948642fb62a56ab0e7db8c2b_133065.c: In function
'probe_1422':
/tmp/stapI6MOvi/stap_6d7c9a6d948642fb62a56ab0e7db8c2b_133065.c:2569: warning:
's0' is used uninitialized in this function
make[1]: *** [/tmp/stapI6MOvi/stap_6d7c9a6d948642fb62a56ab0e7db8c2b_133065.o]
Error 1
make: *** [_module_/tmp/stapI6MOvi] Error 2
Pass 4: compiled C into "stap_6d7c9a6d948642fb62a56ab0e7db8c2b_133065.ko" in
17790usr/4530sys/22241real ms.
Pass 4: compilation failed.  Try again with another '--vp 0001' option.
$ stap -V
SystemTap translator/driver (version 0.8/0.131 commit d1d11e96 + changes)
Copyright (C) 2005-2008 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
$ gcc -v
Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --enable-shared --enable-threads=posix
--disable-checking --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-9.0.1)




-- 


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.

  reply	other threads:[~2009-02-03  5:36 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 ` wenji dot huang at oracle dot com [this message]
2009-02-03 14:07 ` [Bug translator/6979] " 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
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=20090203053644.20035.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).