Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Couple issues with DSF


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx 
> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Dmitry Smirnov
> Sent: Wednesday, February 11, 2009 2:07 PM
> To: CDT General developers list.
> Subject: Re: [cdt-dev] Couple issues with DSF
> >> Well, that means that I have to debug GDB again...
> >> BTW, -stack-list-frames is a MI command, so I cannot test 
> this case in
> >> command-line debugger, isn't it?
> >
> > Sure.  You can start the debugging in MI mode: gdb -i mi
> > Even easier, you can run an MI command outside of MI mode like this:
> > interpreter-exec mi -stack-list-frames
> Could you please take a look at
> ? I had posted a
> question in that list and have got a reply. As I remember DSF debugger
> does not have verbose console mode?

I'm sure you saw my answer by now.
Basically, when issueing an MI command in the DSF-GDB console, the
output is not shown in that console!  I never realized that.
You need to enable traces to see the output.

You can get those 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

I will work on the Verbose console mode bug very soon:

Back to the top