Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Marc Khouzam" <marc.khouzam@ericsson.com>
To: "Marc Khouzam" <marc.khouzam@ericsson.com>,
	        "Vladimir Prus" <vladimir@codesourcery.com>,
	<gdb@sources.redhat.com>
Subject: RE:  Re: Problem with -stack-list-frames
Date: Wed, 11 Feb 2009 19:11:00 -0000	[thread overview]
Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06E855E1@ecamlmw720.eamcs.ericsson.se> (raw)
In-Reply-To: <6D19CA8D71C89C43A057926FE0D4ADAA067F0360@ecamlmw720.eamcs.ericsson.se>

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
> 
> 


      parent reply	other threads:[~2009-02-11 19:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-11 17:55 Dmitry Smirnov
2009-02-11 18:57 ` Vladimir Prus
2009-02-11 19:03   ` Daniel Jacobowitz
2009-02-11 19:09   ` Marc Khouzam
     [not found]   ` <6D19CA8D71C89C43A057926FE0D4ADAA067F0360@ecamlmw720.eamcs.ericsson.se>
2009-02-11 19:11     ` Marc Khouzam [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6D19CA8D71C89C43A057926FE0D4ADAA06E855E1@ecamlmw720.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=gdb@sources.redhat.com \
    --cc=vladimir@codesourcery.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox