(2012/10/04 1:00), Mark Wielaard wrote:
> On Wed, 2012-10-03 at 09:53 -0400, Steven Rostedt wrote:
>> On Wed, 2012-10-03 at 21:17 +0900, Masami Hiramatsu wrote:
>>> <1><9a58>: Abbrev Number: 86 (DW_TAG_subprogram)
>>> <9a59> DW_AT_external: 1
>>> <9a59> DW_AT_name: (indirec
On Wed, 2012-10-03 at 09:53 -0400, Steven Rostedt wrote:
> On Wed, 2012-10-03 at 21:17 +0900, Masami Hiramatsu wrote:
> > <1><9a58>: Abbrev Number: 86 (DW_TAG_subprogram)
> > <9a59> DW_AT_external: 1
> > <9a59> DW_AT_name: (indirect string, offset: 0xd82):
> > unregister_d
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_d
(2012/10/03 21:27), Andi Kleen wrote:
> On Wed, Oct 03, 2012 at 09:17:07PM +0900, Masami Hiramatsu wrote:
>> Add a workaround for GCC -mfentry option. This enables perf
>> probe to find function parameters(arguments) at given function
>> entry point again.
>
> Could you please file a gcc PR about
On Wed, Oct 03, 2012 at 09:17:07PM +0900, Masami Hiramatsu wrote:
> Add a workaround for GCC -mfentry option. This enables perf
> probe to find function parameters(arguments) at given function
> entry point again.
Could you please file a gcc PR about this?
-Andi
--
To unsubscribe from this list:
Add a workaround for GCC -mfentry option. This enables perf
probe to find function parameters(arguments) at given function
entry point again.
With -mfentry, GCC (I've found this with Red Hat 4.7.0-5 and
Red Hat 4.7.2-2 on Fedora 17) generates odd debuginfo about
variable locations.
Here are examp
6 matches
Mail list logo