From: Pavel Machek <pavel@ucw.cz>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Mateusz Berezecki <mateuszb@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: memory range R/W triggered breakpoints in kernel ?
Date: Mon, 6 Mar 2006 23:00:30 +0100 [thread overview]
Message-ID: <20060306220030.GC4836@elf.ucw.cz> (raw)
In-Reply-To: <20060305233202.GD20768@kvack.org>
On Ne 05-03-06 18:32:02, Benjamin LaHaise wrote:
> On Mon, Mar 06, 2006 at 12:31:29AM +0100, Mateusz Berezecki wrote:
> > Yes but again this is userspace. I was thinking about solution used
> > back in the old days in SoftICE kernel level debugger.
> > It had a BPR command (breakpoint on range) which could monitor
> > up to 400000 bytes of memory range. Unfortunately for me this command
> > works in very old versions of _that_ other OS.
>
> If it is in userspace, then you don't need anything from the kernel.
> mprotect() and catch the resulting SIGSEGV.
SoftICE worked on kernel, too. Not sure how it was hacked up.
Pavel
--
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...
prev parent reply other threads:[~2006-03-06 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 17:00 Mateusz Berezecki
2006-03-05 23:16 ` Benjamin LaHaise
2006-03-05 23:31 ` Mateusz Berezecki
2006-03-05 23:32 ` Benjamin LaHaise
2006-03-06 22:00 ` Pavel Machek [this message]
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=20060306220030.GC4836@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mateuszb@gmail.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
Powered by JetHome