Re: breakpoints and symbol examination problems

["Brian Budge" <brian.budge@gmail.com>]

Hi Michael, Daniel, all -

I built gdb from CVS gdb_6_8-branch, and indeed it fixed my breakpoint
problem.  Unfortunately, I still can't examine local variables.  I get
this interaction, for example:

207		vector< dopVertex<T> > tmpVerts;
(gdb)
208		vector< dopEdge > tmpEdges;
(gdb) p tmpVerts
No symbol "tmpVerts" in current context.

Needless to say, not being able to examine your local variable makes
debugging fairly tricky ;)

So, one down, one to go... not too shabby.  Any more ideas?

Thanks,
  Brian

On Tue, Mar 11, 2008 at 8:24 AM, Brian Budge <brian.budge@gmail.com> wrote:
> Actually, this is already with -O0... at least I think.  I'm not
>  passing any optimization flags.  For debug symbols I'm passing -ggdb.
>
>  I'll try the CVS current top of tree a bit later today.
>
>  Thanks,
>   Brian
>
>
>
>  On Mon, Mar 10, 2008 at 5:52 PM, Michael Snyder <msnyder@specifix.com> wrote:
>  > On Mon, 2008-03-10 at 20:32 -0400, Daniel Jacobowitz wrote:
>  >  > On Mon, Mar 10, 2008 at 05:05:17PM -0700, Brian Budge wrote:
>  >  >
>  >
>  > > > Additionally, I can't seem to examine any "stack" variables once in
>  >  > > these template functions.  I can see member variables, global
>  >  > > variables, and function parameters.
>  >  >
>  >  > This may be fixed, or it may be a compiler bug.  GCC is not very good
>  >  > about emitting local variable information in optimized code.
>  >
>  >  Can you compile with -O0?
>  >
>  >
>  >
>