public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: systemtap@sources.redhat.com
Subject: Warnings without -Wno-unused
Date: Wed, 08 Mar 2006 10:27:00 -0000	[thread overview]
Message-ID: <20060308102702.GA8502@in.ibm.com> (raw)

Hi,

I used Frank's syscall.open example from the systemtap tutorial,
used the -k option and wrote a custom makefile to build the module
later in the /tmp dir. Here is the output:

-----
[root@jataayu stapW5pqzA]# make
make -C /lib/modules/2.6.15-1.1833_FC4.root/build
SUBDIRS=/tmp/stapW5pqzA modules
make[1]: Entering directory
`/usr/src/kernels/2.6.15-1.1833_FC4.root-i686'
  CC [M]  /tmp/stapW5pqzA/stap_2958.o
/tmp/stapW5pqzA/stap_2958.c: In function ‘probe_0’:
/tmp/stapW5pqzA/stap_2958.c:1279: warning: label ‘unlock_’ defined but not used
/tmp/stapW5pqzA/stap_2958.c: In function ‘probe_1’:
/tmp/stapW5pqzA/stap_2958.c:1382: warning: label ‘unlock_’ defined but not used
/tmp/stapW5pqzA/stap_2958.c: In function ‘systemtap_module_init’:
/tmp/stapW5pqzA/stap_2958.c:1480: warning: unused variable ‘probe_point’
/tmp/stapW5pqzA/stap_2958.c: At top level:
/usr/local/share/systemtap/runtime/transport/transport.c:26: warning: ‘_stp_dpid’ defined but not used
/usr/local/share/systemtap/runtime/transport/transport.c:51: warning: ‘_stp_streaming’ defined but not used
/usr/local/share/systemtap/runtime/io.c:161: warning: ‘_stp_dbug’ defined but not used
/usr/local/share/systemtap/runtime/print.c:160: warning: ‘next_fmt’ defined but
not used
  Building modules, stage 2.
  MODPOST
  CC      /tmp/stapW5pqzA/stap_2958.mod.o
  LD [M]  /tmp/stapW5pqzA/stap_2958.ko
  make[1]: Leaving directory
  `/usr/src/kernels/2.6.15-1.1833_FC4.root-i686'
-----

As you see, the warnings are benign (currently) and are supressed 'cos of
-Wno-unused in the Makefile generated by stap. But we should revisit this
issue sometime (sooner rather than later) and fixup wherever possible.

Do we already have a bugzilla for this? If not, should one be opened?

Ananth

             reply	other threads:[~2006-03-08 10:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 10:27 Ananth N Mavinakayanahalli [this message]
2006-03-09 14:09 ` 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=20060308102702.GA8502@in.ibm.com \
    --to=ananth@in.ibm.com \
    --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).