From: "Gui,Jian" <guij@cn.ibm.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Roland McGrath <roland@redhat.com>,
systemtap@sources.redhat.com,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: "no match" semantic error for some existing probe points
Date: Wed, 01 Nov 2006 12:32:00 -0000 [thread overview]
Message-ID: <45486C15.907@cn.ltcfwd.linux.ibm.com> (raw)
In-Reply-To: <orbqnr1wzf.fsf@lsd.ic.unicamp.br>
Alexandre Oliva wrote:
> Indeed, but this is an inlined call of ptrace_disabled. What we're
> missing is info about the clear_single_step() inlined call. However,
> in my kernel source tree, clear_single_step is a macro, not a
> function, so you won't get debug info for it without -g3 and, even
> then, you may not get any line numbers whatsoever for the function
> that does nothing but call a macro.
In 2.6.18.1, clear_single_step is defined as an inlined call in
arch/powerpc/kernel/ptrace.c (ppc64) or
arch/powerpc/kernel/ptrace.c (ppc32). Although it is also defined
as macro in arch/powerpc/kernel/traps.c, I think ptrace_disable is
using its inlined call definition.
>
> I'm going to need preprocessed sources, a compilation command line and
> a compiler version number in order to try to get more detailed info
> and fix the compiler bug, if there is one.
>
> Ideally, such info should be in a Systemtap bug report at
> sources.redhat.com or bugzilla.redhat.com.
>
Thanks. I've opened bug 3441 for this and attached some data.
http://sourceware.org/bugzilla/show_bug.cgi?id=3441
Please let me know if more info is needed.
-Guijian
next prev parent reply other threads:[~2006-11-01 9:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 10:17 Gui,Jian
2006-10-17 20:55 ` Frank Ch. Eigler
2006-10-18 4:00 ` Gui,Jian
2006-10-19 7:40 ` Gui,Jian
2006-10-24 17:58 ` Roland McGrath
2006-10-30 6:12 ` Gui,Jian
2006-10-30 22:07 ` Roland McGrath
2006-11-01 7:03 ` Alexandre Oliva
2006-11-01 12:32 ` Gui,Jian [this message]
2006-11-07 7:52 ` Alexandre Oliva
2006-11-07 14:34 ` Gui,Jian
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=45486C15.907@cn.ltcfwd.linux.ibm.com \
--to=guij@cn.ibm.com \
--cc=aoliva@redhat.com \
--cc=fche@redhat.com \
--cc=roland@redhat.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).