Messages in this thread | | | Date | Mon, 6 Mar 2006 23:00:30 +0100 | From | Pavel Machek <> | Subject | Re: memory range R/W triggered breakpoints in kernel ? |
| |
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... - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |