From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23460 invoked by alias); 11 Feb 2009 19:09:26 -0000 Received: (qmail 23450 invoked by uid 22791); 11 Feb 2009 19:09:25 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from imr1.ericy.com (HELO imr1.ericy.com) (198.24.6.9) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 11 Feb 2009 19:09:19 +0000 Received: from eusrcmw750.eamcs.ericsson.se (eusrcmw750.exu.ericsson.se [138.85.77.50]) by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id n1BJFU6E014318; Wed, 11 Feb 2009 13:15:34 -0600 Received: from ecamlmw720.eamcs.ericsson.se ([142.133.1.72]) by eusrcmw750.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 11 Feb 2009 13:09:02 -0600 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Re: Problem with -stack-list-frames Date: Wed, 11 Feb 2009 19:09:00 -0000 Message-ID: <6D19CA8D71C89C43A057926FE0D4ADAA06E855DD@ecamlmw720.eamcs.ericsson.se> In-Reply-To: A References: A From: "Marc Khouzam" To: "Vladimir Prus" , X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-02/txt/msg00096.txt.bz2 =20 > From: Vladimir Prus > Sent: Wednesday, February 11, 2009 1:57 PM > To: gdb@sources.redhat.com > Subject: Re: Problem with -stack-list-frames >=20 > Please enable the verbose mode in the console -- there's a=20 > 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=20 > DSF thinks it's > CLI command, and sends something not right. >=20 > And this might be unrelated to whatever problem you are=20 > 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=20 -debug ~/dsf.debug.options where dsf.debug.options contains org.eclipse.dd.mi/debug =3D true org.eclipse.cdt.dsf.gdb/debug =3D true