From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@elte.hu>, Michal Marek <mmarek@suse.cz>,
Andi Kleen <andi@firstfloor.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Paul Mackerras <paulus@samba.org>,
systemtap@sourceware.org, yrl.pp-manager.tt@hitachi.com
Subject: Re: [PATCH -tip ] [BUGFIX] perf probe: Add a workaround for GCC -mfentry
Date: Wed, 03 Oct 2012 09:53:55 -0400 [thread overview]
Message-ID: <1349272435.22822.165.camel@gandalf.local.home> (raw)
In-Reply-To: <20121003121707.4186.28696.stgit@ltc138.sdl.hitachi.co.jp>
On Wed, 2012-10-03 at 21:17 +0900, Masami Hiramatsu wrote:
> Here are examples:
> -----
> <1><9a58>: Abbrev Number: 86 (DW_TAG_subprogram)
> <9a59> DW_AT_external : 1
> <9a59> DW_AT_name : (indirect string, offset: 0xd82): unregister_di
> e_notifier
> <9a5d> DW_AT_decl_file : 1
> <9a5e> DW_AT_decl_line : 551
> <9a60> DW_AT_prototyped : 1
> <9a60> DW_AT_type : <0x7c>
> <9a64> DW_AT_low_pc : 0x740
> <9a6c> DW_AT_high_pc : 0x75a
> <9a74> DW_AT_frame_base : 1 byte block: 9c (DW_OP_call_frame_cfa)
> <9a76> DW_AT_GNU_all_call_sites: 1
> <9a76> DW_AT_sibling : <0x9aac>
> <2><9a7a>: Abbrev Number: 87 (DW_TAG_formal_parameter)
> <9a7b> DW_AT_name : nb
> <9a7e> DW_AT_decl_file : 1
> <9a7f> DW_AT_decl_line : 551
> <9a81> DW_AT_type : <0x2a96>
> <9a85> DW_AT_location : 0x172f (location list)
> ...
> 0000172f 0000000000000745 0000000000000750 (DW_OP_reg5 (rdi))
> 0000172f 0000000000000750 0000000000000757 (DW_OP_reg4 (rsi))
> 0000172f 0000000000000757 000000000000075a (DW_OP_GNU_entry_value: (DW_OP_reg5 (rdi)); DW_OP_stack_value)
> 0000172f <End of list>
> -----
>
> As you can see, the location of the parameter "nb", starts from 0x745
> but unregister_die_notifier() function itself starts from 0x740.
Um, no I can't see. I guess I need to go and read up on DWARF formats.
Any good recommended links?
A quick google gives me:
http://en.wikipedia.org/wiki/DWARF
http://wiki.dwarfstd.org/index.php?title=Dwarf_FAQ
http://www.eagercon.com/dwarf/dwarf-2.0.0.pdf
Is this what you recommend reading? Or is there better documentation?
-- Steve
next prev parent reply other threads:[~2012-10-03 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:17 [PATCH -tip ] [BUGFIX] perf probe: Add a workaround for GCC -mfentry Masami Hiramatsu
2012-10-03 12:27 ` Andi Kleen
2012-10-03 13:12 ` Masami Hiramatsu
2012-10-03 13:53 ` Steven Rostedt [this message]
2012-10-03 16:00 ` Mark Wielaard
2012-10-04 1:55 ` Masami Hiramatsu
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=1349272435.22822.165.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=paulus@samba.org \
--cc=systemtap@sourceware.org \
--cc=yrl.pp-manager.tt@hitachi.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 NNTP newsgroup(s).