From: Sami Wagiaalla <swagiaal@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: Dwarf expertise needed
Date: Thu, 19 Jul 2007 15:40:00 -0000 [thread overview]
Message-ID: <469F85DF.4050000@redhat.com> (raw)
In-Reply-To: <20070718090247.A712B4D05CF@magilla.localdomain>
> [...] if you are displaying the running code in an inlined instance
> and want to visualize "this code inlined into here",
In the future we are going to do that.
> or are synthesizing
> fictional call frames for a semantic backtrace including inlined calls.
>
This is what I am currently doing :).
But something else just occurred to me. The way I find a function
(regular not inlined ) corresponding to a frame is I call
dwarf_getscopes at frame address, then traverse up the scopes list until
I hit the first DW_TAG_Subprogram. For this I will also need a physical
scope list rather than a lexical one, because if a function in the list
happens to be inlined between the narrowest scope and the Subprogram I
will not find the reference to my Subprogram.
next prev parent reply other threads:[~2007-07-19 15:40 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
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 [this message]
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=469F85DF.4050000@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).