Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Sascha" <sascha@pasalacqua.de>
To: <gdb@sourceware.org>
Subject: MI, remote protocol and error codes
Date: Thu, 22 Feb 2007 19:58:00 -0000	[thread overview]
Message-ID: <000301c756b7$5c359d90$02b2a8c0@insanenotebook> (raw)

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)
?
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. 

Is there any way (or any plans) to report error codes over MI ? Or is there
a different solution ?

Thanks

Sascha


             reply	other threads:[~2007-02-22 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-22 19:58 Sascha [this message]
2007-02-22 22:26 ` Daniel Jacobowitz
2007-02-23 17:12   ` AW: " Sascha

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='000301c756b7$5c359d90$02b2a8c0@insanenotebook' \
    --to=sascha@pasalacqua.de \
    --cc=gdb@sourceware.org \
    /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