On Mon, 3 Mar 2008, Julian Seward wrote: > On Monday 03 March 2008 04:17, Nicholas Nethercote wrote: >> On Mon, 3 Mar 2008, Julian Seward wrote: >>> Location 0x7feffba09 is 1 byte inside a[3].xyzzy[21].c2[2], >>> declared at varinfo4.c:45, in frame #1 of thread 1 >> >> What's the frame number? > > It tries to locate an address in all call frames of all thread > stacks. So "frame #1" is really a cryptic way to say "1 frame > down from the top of stack of thread 1". I found it hard to > think of an equally concise but less cryptic way to phrase it.
So it's the top stack frame on thread 1's stack? Or the 2nd frame? Can you summarise the different messages that are possible now -- eg. stack variables, static (global) variables, static (local) variables, heap variables, etc? That might help determine if the messages could be made clearer. Nick ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Valgrind-developers mailing list Valgrind-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-developers
