public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: ch huang <justlooks@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: problem in User-Space Probing
Date: Tue, 06 Mar 2012 04:49:00 -0000	[thread overview]
Message-ID: <20120306044728.GA13284@linux.vnet.ibm.com> (raw)
In-Reply-To: <CACeqxwT-v_fXLYdm6+FcCH5E+TSWQifbkY_n=Jnb7hk+xpa5+w@mail.gmail.com>

> 
> probe process("/root/test").function("my_out"){
> printf("i in %s\n",pp())
> }
> probe process("/root/test").function("my_out").return{
> printf("back from %s\n",probefunc())
> }
> when i run this script i find some warning information
> 
> # stap exec.stp
> /usr/local/share/systemtap/runtime/uprobes/uprobes.c: In function
> ?uprobe_report_exec?:
> /usr/local/share/systemtap/runtime/uprobes/uprobes.c:2401: warning:
> ?uproc? may be used uninitialized in this function
> /usr/local/share/systemtap/runtime/uprobes/uprobes.c: In function
> ?uprobe_report_exit?:
> /usr/local/share/systemtap/runtime/uprobes/uprobes.c:2101: warning:
> ?uproc? may be used uninitialized in this function
> i in process("/root/test").function("my_out@/root/test.c:4")
> back from my_out
> 
> it seems script works fine ,but i do not know the warning info,is
> there something i missed?
> 

It would have been good if you had given your stap setup details.
I think you are running on a kernel < 2.6.24.

From the code walk through, I dont see a case for uproc being not
initialized.  I think its a compiler bug. 

https://lkml.org/lkml/2011/11/28/287

-- 
Thanks and Regards
Srikar

  reply	other threads:[~2012-03-06  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06  3:17 ch huang
2012-03-06  4:49 ` Srikar Dronamraju [this message]
2012-03-06 15:56 ` Frank Ch. Eigler

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=20120306044728.GA13284@linux.vnet.ibm.com \
    --to=srikar@linux.vnet.ibm.com \
    --cc=justlooks@gmail.com \
    --cc=systemtap@sourceware.org \
    /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).