From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29434 invoked by alias); 22 Feb 2007 19:57:08 -0000 Received: (qmail 29426 invoked by uid 22791); 22 Feb 2007 19:57:08 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Thu, 22 Feb 2007 19:56:59 +0000 Received: from dsl093-172-095.pit1.dsl.speakeasy.net ([66.93.172.95] helo=caradoc.them.org) by nevyn.them.org with esmtp (Exim 4.63) (envelope-from ) id 1HKK3k-0001QA-Bu; Thu, 22 Feb 2007 14:56:56 -0500 Received: from drow by caradoc.them.org with local (Exim 4.63) (envelope-from ) id 1HKK3j-000729-Ql; Thu, 22 Feb 2007 14:56:55 -0500 Date: Thu, 22 Feb 2007 22:26:00 -0000 From: Daniel Jacobowitz To: Sascha Cc: gdb@sourceware.org Subject: Re: MI, remote protocol and error codes Message-ID: <20070222195655.GA26759@caradoc.them.org> Mail-Followup-To: Sascha , gdb@sourceware.org References: <000301c756b7$5c359d90$02b2a8c0@insanenotebook> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000301c756b7$5c359d90$02b2a8c0@insanenotebook> User-Agent: Mutt/1.5.13 (2006-08-11) 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: 2007-02/txt/msg00241.txt.bz2 On Thu, Feb 22, 2007 at 08:26:32PM +0100, Sascha wrote: > Hi, > > I'm currently using GDB (CS 6.5) in a situation like this: > > C/C++ IDE ---[MI]---> GDB ---[Remote Protocol]---> Remote stub > > Am I right and GDB does not care at all about remote error codes (ENN reply) > ? I believe that's true. > The remote stub supports breakpoints, but there are situations when a > breakpoint has to be rejected (depending on internal state). When the stub > replies with an error code, GDB won't resume - which is good - but it just > reports "Protocol error: Z0 (software-breakpoint) conflicting enabled > responses". The MI protocol does not report the error code, so the IDE does > not get to know why the breakpoint got rejected. Are you sure you're replying with an error code, not with an empty packet? There should be no other way to get this message. > Is there any way (or any plans) to report error codes over MI ? Or is there > a different solution ? There's no plan for this, but it's come up before, so something may be necessary in the future. -- Daniel Jacobowitz CodeSourcery