From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Keep breakpoints always inserted.
Date: Sat, 01 Dec 2007 15:43:00 -0000 [thread overview]
Message-ID: <u63zi1kwc.fsf@gnu.org> (raw)
In-Reply-To: <200712011423.21957.vladimir@codesourcery.com> (message from Vladimir Prus on Sat, 1 Dec 2007 14:23:21 +0300)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sat, 1 Dec 2007 14:23:21 +0300
>
>
> This patch makes breakpoint always inserted. There are not
> regressions on x86. I think the patch is almost ready,
> and comments are appreciated.
>
> It's RFC, and not RFA because:
>
> - There's no option to disable always-inserted mode
> - I would like to add a separate option to report
> breakpoint insert/remove operations, to facilitate testing
> now and in future
> - I just want the code to "soak" for about a week
Please also consider whether something in gdbint.texinfo needs to be
updated as result of this change (unless you already considered that).
next prev parent reply other threads:[~2007-12-01 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 11:23 Vladimir Prus
2007-12-01 15:43 ` Eli Zaretskii [this message]
2007-12-01 16:11 ` Vladimir Prus
2007-12-01 20:59 ` Eli Zaretskii
2007-12-14 17:08 ` 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=u63zi1kwc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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