RE: Re: Problem with -stack-list-frames

["Marc Khouzam" <marc dot khouzam at ericsson dot com>]

I just realized something, please see below. 

> -----Original Message-----
> From: Marc Khouzam 
> Sent: Wednesday, February 11, 2009 2:09 PM
> To: 'Vladimir Prus'; 'gdb@sources.redhat.com'
> Subject: RE: Re: Problem with -stack-list-frames
> 
>  
> > From: Vladimir Prus
> > Sent: Wednesday, February 11, 2009 1:57 PM
> > To: gdb@sources.redhat.com
> > Subject: Re: Problem with -stack-list-frames
> > 
> > Please enable the verbose mode in the console -- there's a 
> > button in the
> > toolbar. This will tell exactly what the error is -- and 
> I'm 51% sure
> > the problem is that you are trying to send MI command, and 
> > DSF thinks it's
> > CLI command, and sends something not right.

DSF sends it correctly but the output is not shown in the console
that is why it seems blank.  You need the traces to see the
output.  See previous mail (or below) to turn them on.

I'm gonna have to have DSF-GDB print the output of console
commands to the console....


> > 
> > And this might be unrelated to whatever problem you are 
> > having in the first
> > place. CDI  debuggers have a way to enable verbose console 
> mode in the
> > launch configuration. Please do that in DSF and then see if 
> something
> > is wrong with any GDB response.
> 
> Yeah... I didn't get to implementing the verbose console yet :-(
> But I've been feeling the pressure for it so I've bumped it up on my
> todo list.
> 
> You can still get traces by launching eclipse with 
> -debug ~/dsf.debug.options
> 
> where dsf.debug.options contains
> 
> org.eclipse.dd.mi/debug = true
> org.eclipse.cdt.dsf.gdb/debug = true
> 
>