From: Alexandre Oliva <aoliva@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: "Gui,Jian" <guij@cn.ibm.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 07:03:00 -0000 [thread overview]
Message-ID: <orbqnr1wzf.fsf@lsd.ic.unicamp.br> (raw)
In-Reply-To: <20061030205508.0F8C7180051@magilla.sf.frob.com> (Roland McGrath's message of "Mon, 30 Oct 2006 12:55:07 -0800 (PST)")
On Oct 30, 2006, Roland McGrath <roland@redhat.com> wrote:
>> <2><4673b>: Abbrev Number: 49 (DW_TAG_inlined_subroutine)
>> DW_AT_abstract_origin: <467d3>
>> DW_AT_low_pc : 0x9db0
>> DW_AT_high_pc : 0x9de8
>> DW_AT_call_file : 0
>> DW_AT_call_line : 0
>>
>> Does this mean the compiler didn't produce such information and
>> we cannot handle this in systemtap?
> This indeed is the compiler giving us no useful information here.
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.
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,
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-11-01 6:51 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 [this message]
2006-11-01 12:32 ` Gui,Jian
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=orbqnr1wzf.fsf@lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=fche@redhat.com \
--cc=guij@cn.ibm.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).