Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Sascha" <sascha@pasalacqua.de>
To: "'Michael Snyder'" <Michael.Snyder@palmsource.com>
Cc: "'Daniel Jacobowitz'" <drow@false.org>, <gdb@sourceware.org>
Subject: Re: Disabling breakpoints does not work if rejected from remotestub
Date: Tue, 06 Mar 2007 07:38:00 -0000	[thread overview]
Message-ID: <004401c75fc2$698386b0$02b2a8c0@insanenotebook> (raw)
In-Reply-To: <1173125452.29183.17.camel@localhost.localdomain>

Hi

>>However, the more serious error is that at this point, the
"run" (or "step") command is aborted, returning to the gdb
prompt, but without removing the breakpoints.  The error handling
code at this point ought to remove all of the breakpoints that
have been inserted.

I guess GDB does not have to remove the breakpoints at that point - as long
as it will remember them later on. You simply have to compare the "DELETE
BP1/BP2" section and the "DISABLE BP1/BP2" section in the log.

_Deleting_ the breakpoints causes GDB to send the required "z0" (bp remove)
packets for those breakpoints which have been inserted already.

_Disabling_ the breakpoints does nothing. No "z0" packets were send to the
stub.

So I guess the fix is to make GDB send the required z0 packets for disabled
breakpoints - just like it does for deleted breakpoints. 

Sascha



  reply	other threads:[~2007-03-06  7:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-27 11:55 Disabling breakpoints does not work if rejected from remote stub Sascha
2007-02-27 12:52 ` Daniel Jacobowitz
2007-02-27 19:29   ` Sascha
2007-03-06  1:06     ` Michael Snyder
2007-03-06  7:38       ` Sascha [this message]
2007-03-06 19:44         ` Disabling breakpoints does not work if rejected from remotestub Michael Snyder

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='004401c75fc2$698386b0$02b2a8c0@insanenotebook' \
    --to=sascha@pasalacqua.de \
    --cc=Michael.Snyder@palmsource.com \
    --cc=drow@false.org \
    --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