From: Vladimir Prus <vladimir@codesourcery.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Try2: Ignore breakpoints when reading memory.
Date: Mon, 10 Mar 2008 20:57:00 -0000 [thread overview]
Message-ID: <200803102357.23694.vladimir@codesourcery.com> (raw)
In-Reply-To: <20080310204242.GA14908@caradoc.them.org>
On Monday 10 March 2008 23:42:42 Daniel Jacobowitz wrote:
> On Sun, Feb 24, 2008 at 05:50:39PM +0300, Vladimir Prus wrote:
> >
> > This a second attempt at making gdb always ignore
> > any memory breakpoints that are inserted and show the original
> > memory content. This patch is the immediate prerequisite for the
> > patch that makes breakpoints always inserted.
> >
> > Unlike the previous patch, there's a mechanism to:
> > 1. Control the new behaviour from command line.
>
> Do you think we need the option is useful? I think we'll want one for
> leave-breakpoints-inserted mode, which is a bigger change, but this
> patch should only affect GDB internals.
I've added the option as it might be helpful to see real
memory content, say, when diagnosing problems with gdb/stub itself.
>
> > +static void
> > +restore_show_memory_breakpoints (void *arg)
> > +{
> > + show_memory_breakpoints = (int)arg;
> > +}
>
> This will fail with -Werror on a 64-bit host.
Ah, right.
> That leaves the attached patch. Tested on x86_64-linux, no
> regressions. How's it look? I deleted read_memory_nobpt
> entirely.
I think it's good.
- Volodya
next prev parent reply other threads:[~2008-03-10 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-24 14:58 Vladimir Prus
2008-02-24 20:08 ` Eli Zaretskii
2008-02-25 19:30 ` Michael Snyder
2008-02-26 0:53 ` Joel Brobecker
2008-03-10 20:43 ` Daniel Jacobowitz
2008-03-10 20:57 ` Vladimir Prus [this message]
2008-03-13 12:22 ` Daniel Jacobowitz
2008-03-13 13:19 ` 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=200803102357.23694.vladimir@codesourcery.com \
--to=vladimir@codesourcery.com \
--cc=drow@false.org \
--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