public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Sami Wagiaalla <swagiaal@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: Dwarf expertise needed
Date: Tue, 17 Jul 2007 17:07:00 -0000	[thread overview]
Message-ID: <469CF739.7000706@redhat.com> (raw)
In-Reply-To: <20070619213109.8D9BB4D05D3@magilla.localdomain>

Roland McGrath wrote:
>> Okay it sounds like I missunderstood what addrdie does. I guess what I 
>> am trying to do is find the narrowest scope which contains the given pc. 
>> Is there a way to get all dies whos ranges contain the pc maybe ? The 
>> problem I am trying to solve is given a pc find the inlined/concrete 
>> function that contains it.
>>     
>
> This is what dwarf_getscopes is for.
>   
Okay so I have been looking at dwarf_getscopes.c trying to find a fix 
for  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=230235.

Now i can fudge the function pc_record to return the results that I am 
expecting but it looks like it is trying to do something different from 
what I understand when it comes to inlined functions.

It looks like getscopes is trying to return the scopes from narrowest up 
to the scope before the concrete inlined instance then the abstract 
definition of the concrete instance, and then the scopes that contain 
that. Is this a correct understanding of the code ?

What I am expecting it to return is the the scopes from narrowest to and 
including the scope corresponding to the concrete inlined instance, then 
the function within which it has been inlined and the scopes containing 
that; as per the dwarf spec. Is this a correct understanding of what the 
function /should/ do ? And should I fix the function, write a parallel 
one that does what i want, or is there another code pathway to get it ?


Cheers,
   Sami Wagiaalla

  reply	other threads:[~2007-07-17 17:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-19 15:22 Sami Wagiaalla
2007-06-19 15:46 ` Sami Wagiaalla
2007-06-19 18:28   ` Sami Wagiaalla
2007-06-19 21:11     ` Sami Wagiaalla
2007-06-19 21:27       ` Roland McGrath
2007-06-19 21:31         ` Sami Wagiaalla
2007-06-19 21:31           ` Roland McGrath
2007-07-17 17:07             ` Sami Wagiaalla [this message]
2007-07-18  9:03               ` Roland McGrath
2007-07-18 15:38                 ` Sami Wagiaalla
2007-07-18 22:43                   ` Roland McGrath
2007-07-19 15:31                     ` Sami Wagiaalla
2007-07-21  0:29                       ` Roland McGrath
2007-07-26 15:42                         ` Sami Wagiaalla
2007-08-07  9:04                           ` Roland McGrath
2007-08-09 17:06                             ` Sami Wagiaalla
2007-07-19 15:40                 ` Sami Wagiaalla
2007-06-19 21:38           ` Sami Wagiaalla
2007-06-19 21:58         ` Sami Wagiaalla

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=469CF739.7000706@redhat.com \
    --to=swagiaal@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=roland@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).