Re: Debugging C++ Function Calls

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Lawrence" == Lawrence Crowl <crowl@googlers.com> writes:

Lawrence> Hm.  I haven't thought about this deeply, but I think SFINAE may
Lawrence> not be less of an issue because it serves to remove candidates
Lawrence> from potential instantiation, and gdb won't be instantiating.
Lawrence> The critical distinction is that I'm not trying to call arbitrary
Lawrence> expressions (which would have a SFINAE problem) but call expressions
Lawrence> that already appear in the source.

Thanks.
I will think about it.

Lawrence> I agree that the best long-term solution is an integrated compiler,
Lawrence> interpreter, and debugger.  That's not likely to happen soon.  :-)

Sergio is re-opening our look into reusing GCC.
Keith Seitz wrote a GCC plugin to try to let us farm out
expression-parsing to the compiler.  This has various issues, some
because gdb allows various C++ extensions that are useful when
debugging; and also g++ was too slow.
Even if g++ can't be used we at least hope this time to identify some of
the things that make it slow and file a few bug reports...

Lawrence> I don't know anything about gdb internals, so it may not be helpful
Lawrence> for me to look at it.

Sure, but maybe for a critique of the approach.  But only if you are
interested.

Tom