Re: memory range R/W triggered breakpoints in kernel ?

[Benjamin LaHaise]

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.

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@xxxxxxxxx>.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/