From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Keep breakpoints always inserted.
Date: Thu, 24 Apr 2008 11:22:00 -0000 [thread overview]
Message-ID: <fup317$baa$1@ger.gmane.org> (raw)
In-Reply-To: <20080423201007.GA14383@caradoc.them.org>
Daniel Jacobowitz wrote:
> On Wed, Apr 23, 2008 at 08:45:54PM +0100, Pedro Alves wrote:
>> I've tested this patch on top of Vladimir's and with displaced
>> stepping on, on x86-pc-linux-gnu. Luis tested it on PPC, where
>> it also fixed things.
>
> OK when the original patch is committed.
Well, I have an obvious adjustment to the original patch to fix this
issue in a more clear way -- my making should_insert_location not
return false for an already inserted location.
>> Anyone object to adding debug output support to the
>> breakpoint module? I've writen something similar twice
>> already, and I'd like to not have to a third time. Something
>> like "set debug breakpoint 1", where it prints
>> "breakpoints inserted", "breakpoints removed", etc.
>
> Sounds like a good idea to me.
Likewise.
- Volodya
next prev parent reply other threads:[~2008-04-24 4:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 14:18 Vladimir Prus
2008-03-10 21:09 ` Daniel Jacobowitz
2008-03-14 20:22 ` Vladimir Prus
2008-03-15 10:13 ` Vladimir Prus
2008-03-15 15:10 ` Eli Zaretskii
2008-04-02 13:02 ` Vladimir Prus
2008-04-02 18:18 ` Eli Zaretskii
2008-03-17 22:21 ` Daniel Jacobowitz
2008-03-18 4:15 ` Eli Zaretskii
2008-03-18 6:06 ` Vladimir Prus
2008-04-03 18:10 ` Vladimir Prus
2008-04-07 15:32 ` Daniel Jacobowitz
2008-04-09 23:45 ` Vladimir Prus
2008-04-10 8:16 ` Luis Machado
2008-04-17 16:50 ` Daniel Jacobowitz
2008-04-23 21:18 ` Pedro Alves
2008-04-23 21:24 ` Daniel Jacobowitz
2008-04-24 11:22 ` Vladimir Prus [this message]
2008-04-24 12:10 ` Vladimir Prus
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='fup317$baa$1@ger.gmane.org' \
--to=vladimir@codesourcery.com \
--cc=gdb-patches@sources.redhat.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