Re: Debugging C++ Function Calls

2013-03-27 Thread Tom Tromey
> "Lawrence" == Lawrence Crowl writes: Lawrence> Are the symbol searches specific to the scope context, or does it Lawrence> search all globally defined symbols? I am not totally certain in this case, but in gdb many searches are global, so that "print something" works even if "something" is

Re: Debugging C++ Function Calls

2013-03-26 Thread Lawrence Crowl
On 3/25/13, Tom Tromey wrote: > I think the intro text of this message provides the best summary > of the approach: > > http://sourceware.org/ml/gdb-patches/2010-07/msg00284.html Are the symbol searches specific to the scope context, or does it search all globally defined symbols? If you recreat

Re: Debugging C++ Function Calls

2013-03-26 Thread Gabriel Dos Reis
On Tue, Mar 26, 2013 at 3:02 PM, Tom Tromey wrote: > Richard> Did you consider using clang? > Richard> > > We may look at it after re-examining g++. > I think there are some reasons to prefer gcc. Yes, obviously :-) -- Gaby

Re: Debugging C++ Function Calls

2013-03-26 Thread Tom Tromey
Richard> Did you consider using clang? Richard> We may look at it after re-examining g++. I think there are some reasons to prefer gcc. Tom

Re: Debugging C++ Function Calls

2013-03-26 Thread Richard Biener
On Mon, Mar 25, 2013 at 7:20 PM, Tom Tromey wrote: >> "Lawrence" == Lawrence Crowl 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 gd

Re: Debugging C++ Function Calls

2013-03-25 Thread Tom Tromey
> "Lawrence" == Lawrence Crowl writes: Tom> Sure, but maybe for a critique of the approach. But only if you are Tom> interested. Lawrence> Sure, send it. I think the intro text of this message provides the best summary of the approach: http://sourceware.org/ml/gdb-patches/2010-07/msg00284

Re: Debugging C++ Function Calls

2013-03-25 Thread Lawrence Crowl
On 3/25/13, Tom Tromey wrote: >> "Lawrence" == Lawrence Crowl 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 instantiat

Re: Debugging C++ Function Calls

2013-03-25 Thread Tom Tromey
> "Lawrence" == Lawrence Crowl 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

Debugging C++ Function Calls

2013-03-25 Thread Lawrence Crowl
On 3/25/13, Tom Tromey wrote: >> "Lawrence" == Lawrence Crowl writes: > > Lawrence> My model is that I should be able to cut and paste an expression > Lawrence> from the source to the debugger and have it work. I concede that > Lawrence> C++ function overload resolution is a hard problem. H