This is the mail archive of the
frysk@sources.redhat.com
mailing list for the frysk project.
Re: stack call
- From: Andrew Cagney <cagney at redhat dot com>
- To: Andrew Cagney <cagney at redhat dot com>
- Cc: Sami Wagiaalla <swagiaal at redhat dot com>, Phil Muldoon <pmuldoon at redhat dot com>, Nurdin Premji <npremji at redhat dot com>, Stan Cox <scox at redhat dot com>, frysk <frysk at sources dot redhat dot com>
- Date: Mon, 07 May 2007 12:08:05 -0400
- Subject: Re: stack call
- References: <463F331C.8050302@redhat.com>
Notes:
Current state:
npremji, pmuldoon: core and proc models + ABI backtrace
- npremji is working on getting the ABI stack-backtrace, provided by
libunwind, working using frysk to get memory et.al.
- pmuldoon and npremji are looking at how ELFUTILS is bound so it
too uses frysk to get memory et.al.
- pmuldoon is filling in the core file side of a frysk.proc model
this will give us an ABI stack backtrace on both core files and on live
processes; a simple test is "fstack" of a core file
scox: variables, types, locations and expressions
- getting the type system filled out and working when the variable
is in static memory (i.e., avoiding complexities of location expressions)
- also other type system issues such as tab competion
this will get us the ability to display all variables (but with
limitations on the variables location)
Going forward:
sami to look at the .debug_info code so that frysk's stack model is
extended to include source level line and function information vis:
- knowledge that there are multiple functions for a frame
- knowledge that a function has its line/file
- ways to display et.al. same
- work with make on how to use this in the stepping code with mcvet
; will try to get things so that in-line functions by default behave
like macros; i.e., step over when next
this will give us the higher level backtrace and start to allow us to
build out things like scoping and, potentially, variable and other
information
pmuldoon, npremji: keep going with getting low-level core and process
frysk.proc working
scox: continue with type system, perhaps with sami, start to look at
location expression stuff (much overlap).
[side discussion about how elfutils has bindings to return the evaluated
location expression, sweet]
Andrew
Andrew Cagney wrote:
Phil, Nurdin, Sami, Stan,
I'd like to set up a quick call this morning to discuss next steps for
stack-back-tracing. In particular using .debug_info to create a more
detailed back-trace.
I'll reserve 11 Toronto time.
Andrew