From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Aravinda <aravindakidambi@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: GDB library to insert and delete watchpoints
Date: Tue, 01 Dec 2009 05:44:00 -0000 [thread overview]
Message-ID: <8ac60eac0911302144p498711oa2f614bb885c087d@mail.gmail.com> (raw)
In-Reply-To: <26eb53620911301518y13e64bc0g95c6fe3c7b18b0c@mail.gmail.com>
On Mon, Nov 30, 2009 at 3:18 PM, Aravinda <aravindakidambi@gmail.com> wrote:
> Im working on a project that currently requires inserting and deleting
> watchpoints to monitor buffer overruns.
AFAIU, on x86 you can monitor at most 4 addresses, since that's all
the debug registers it got. That makes using HW watchpoints for
overrun detection of dubious value (unless you only care about
overrunning a very small set of buffers).
> I was looking at the
> gdb-internals documentation which talks about a gdb library that can
> be used to do exactly this.
It can't be (at lease not without a lot of work). Please see this
message and thread: http://sourceware.org/ml/gdb/2009-08/msg00003.html
> But I couldnt find more info on this. Im
> looking for a ready to use library to be used with a kernel module
> that allows for modifying the debug registers. kindly point me to any
> sources if it can be done.
AFAICT, such a library does not exist.
Cheers,
--
Paul Pluzhnikov
next parent reply other threads:[~2009-12-01 5:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26eb53620911301516x68ccc0edkf64ba2951c8ce3a3@mail.gmail.com>
[not found] ` <26eb53620911301518y13e64bc0g95c6fe3c7b18b0c@mail.gmail.com>
2009-12-01 5:44 ` Paul Pluzhnikov [this message]
2009-12-01 18:08 ` Dave Korn
2009-12-01 21:14 ` Jan Kratochvil
2009-12-04 8:51 ` Stan Shebs
2009-12-04 16:21 ` Aravinda
2009-12-04 17:11 ` Jan Kratochvil
2009-12-07 21:30 ` Aravinda
2009-12-04 16:38 ` Joel Brobecker
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=8ac60eac0911302144p498711oa2f614bb885c087d@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=aravindakidambi@gmail.com \
--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