* stack call
@ 2007-05-07 14:16 Andrew Cagney
2007-05-07 14:18 ` Sami Wagiaalla
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Andrew Cagney @ 2007-05-07 14:16 UTC (permalink / raw)
To: Sami Wagiaalla, Phil Muldoon, Nurdin Premji, Stan Cox; +Cc: frysk
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
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 14:16 stack call Andrew Cagney
@ 2007-05-07 14:18 ` Sami Wagiaalla
2007-05-07 14:20 ` Phil Muldoon
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Sami Wagiaalla @ 2007-05-07 14:18 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Phil Muldoon, Nurdin Premji, Stan Cox, frysk
> I'll reserve 11 Toronto time.
Count me in.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 14:16 stack call Andrew Cagney
2007-05-07 14:18 ` Sami Wagiaalla
@ 2007-05-07 14:20 ` Phil Muldoon
2007-05-07 15:21 ` Nurdin Premji
2007-05-07 16:08 ` Kris Van Hees
2007-05-07 17:08 ` Andrew Cagney
3 siblings, 1 reply; 8+ messages in thread
From: Phil Muldoon @ 2007-05-07 14:20 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Sami Wagiaalla, Nurdin Premji, Stan Cox, frysk
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.
Ok.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 14:20 ` Phil Muldoon
@ 2007-05-07 15:21 ` Nurdin Premji
0 siblings, 0 replies; 8+ messages in thread
From: Nurdin Premji @ 2007-05-07 15:21 UTC (permalink / raw)
To: Phil Muldoon; +Cc: Andrew Cagney, Sami Wagiaalla, Stan Cox, frysk
Phil Muldoon wrote:
> 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.
>
> Ok.
>
Me too.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 14:16 stack call Andrew Cagney
2007-05-07 14:18 ` Sami Wagiaalla
2007-05-07 14:20 ` Phil Muldoon
@ 2007-05-07 16:08 ` Kris Van Hees
2007-05-07 19:44 ` Andrew Cagney
2007-05-07 17:08 ` Andrew Cagney
3 siblings, 1 reply; 8+ messages in thread
From: Kris Van Hees @ 2007-05-07 16:08 UTC (permalink / raw)
To: Andrew Cagney; +Cc: frysk
A few questions...
1. Is this an open call? I am willing to bet that I am not the only one
who is also interested in this topic and would be quite interested in
technical topics discussion like this (and hopefully able to
contribute to it). If not an open call, err, why not? :)
2. If it is an open call, it might be a good idea to post basic
call-in information, even if things like passcode are best left out
of emails to public mailing lists. Can always put in a reference on
who to ask for the passcode.
3. Can calls like this perhaps be announced a bit more in advance so
people may be able to make arrangements to join the call?
Cheers,
Kris
On Mon, May 07, 2007 at 10:09:32AM -0400, 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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 14:16 stack call Andrew Cagney
` (2 preceding siblings ...)
2007-05-07 16:08 ` Kris Van Hees
@ 2007-05-07 17:08 ` Andrew Cagney
2007-05-10 15:24 ` Sami Wagiaalla
3 siblings, 1 reply; 8+ messages in thread
From: Andrew Cagney @ 2007-05-07 17:08 UTC (permalink / raw)
To: Andrew Cagney
Cc: Sami Wagiaalla, Phil Muldoon, Nurdin Premji, Stan Cox, frysk
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
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 16:08 ` Kris Van Hees
@ 2007-05-07 19:44 ` Andrew Cagney
0 siblings, 0 replies; 8+ messages in thread
From: Andrew Cagney @ 2007-05-07 19:44 UTC (permalink / raw)
To: Kris Van Hees; +Cc: frysk
Kris,
I would assume impromptu call like this use the standard dial-in numbers
and are open (i'll be more explicit next time). And the main goal is to
facilitate a timely non-technical discussion with the immediate
players. For technical discussion, #frysk, frysk@ or Wednesday are
always the preferred channels.
Andrew
Kris Van Hees wrote:
> A few questions...
>
> 1. Is this an open call? I am willing to bet that I am not the only one
> who is also interested in this topic and would be quite interested in
> technical topics discussion like this (and hopefully able to
> contribute to it). If not an open call, err, why not? :)
>
> 2. If it is an open call, it might be a good idea to post basic
> call-in information, even if things like passcode are best left out
> of emails to public mailing lists. Can always put in a reference on
> who to ask for the passcode.
>
> 3. Can calls like this perhaps be announced a bit more in advance so
> people may be able to make arrangements to join the call?
>
> Cheers,
> Kris
>
> On Mon, May 07, 2007 at 10:09:32AM -0400, 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
>>
>>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: stack call
2007-05-07 17:08 ` Andrew Cagney
@ 2007-05-10 15:24 ` Sami Wagiaalla
0 siblings, 0 replies; 8+ messages in thread
From: Sami Wagiaalla @ 2007-05-10 15:24 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Phil Muldoon, Nurdin Premji, Stan Cox, frysk
> 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
Ok so here is a summary of what I will be doing:
As Stan pointed out the above described hierarchy is already in place.
My work will involve, making sure that the structures are populated
using the dwarf information, testing, and providing appropriates
interface for stack examination, and variable inspection.
As Andrew explained test cases will be used to develop, and solidify the
API. And also to test that is is working :)
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2007-05-10 15:23 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-05-07 14:16 stack call Andrew Cagney
2007-05-07 14:18 ` Sami Wagiaalla
2007-05-07 14:20 ` Phil Muldoon
2007-05-07 15:21 ` Nurdin Premji
2007-05-07 16:08 ` Kris Van Hees
2007-05-07 19:44 ` Andrew Cagney
2007-05-07 17:08 ` Andrew Cagney
2007-05-10 15:24 ` Sami Wagiaalla
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).