This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Issues with dwarf APIs

From: Roland McGrath <roland at redhat dot com>
To: Sharyathi Nagesh <sharyath at in dot ibm dot com>
Cc: fche at elastic dot org, systemtap at sources dot redhat dot com, Mohan Kumar M <mohan at in dot ibm dot com>
Date: Wed, 3 Jun 2009 14:20:53 -0700 (PDT)
Subject: Re: Issues with dwarf APIs
References: <4A248804.3070009@in.ibm.com> <20090602225829.E2C97FC3C7@magilla.sf.frob.com> <4A26E794.4010905@in.ibm.com>

>     Regarding the PC, this is definitely not the entry address of the 
> function but the return location from the called function, hence it is 
> between low_pc and high_pc. As I understand that is the right thing to 
> do, giving low_pc or starting address of the function had issues with 
> variable not getting initialized at that instance.

Yes, you have to use the correct exact PC that was stored for that stack frame.
The DWARF info describes how to find a symbolic value in the context of an
exact PC.  For some PC elsewhere in the function, the details may differ hugely.

References:
- Issues with dwarf APIs
  - From: Sharyathi Nagesh
- Re: Issues with dwarf APIs
  - From: Roland McGrath
- Re: Issues with dwarf APIs
  - From: Sharyathi Nagesh

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]