This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: how to examine data with compiler optimization option set?


On Tue, 2008-09-02 at 23:04 -0400, Frank Ch. Eigler wrote:
> Michael Snyder <msnyder@vmware.com> writes:
> 
> > [...]
> > I don't think there is any possibility whatsoever of
> > somehow generating location codes for the variables in
> > the example.
> >
> > Those values are simply not kept anywhere.  GCC will replace
> > them all with the constant, "3".
> 
> You might be surprised.  Some RH engineers are working along these
> lines.  Being able to debug (<=> probe/trace) optimized code is
> becoming more and more important, and gcc is slowly getting into the
> mood to help.

I'm more than willing to be surprised...
it will be a pleasant one.  ;-)



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]