Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751077AbWCEXhZ (ORCPT ); Sun, 5 Mar 2006 18:37:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751901AbWCEXhZ (ORCPT ); Sun, 5 Mar 2006 18:37:25 -0500 Received: from kanga.kvack.org ([66.96.29.28]:23460 "EHLO kanga.kvack.org") by vger.kernel.org with ESMTP id S1751077AbWCEXhZ (ORCPT ); Sun, 5 Mar 2006 18:37:25 -0500 Date: Sun, 5 Mar 2006 18:32:02 -0500 From: Benjamin LaHaise To: Mateusz Berezecki Cc: Linux Kernel Mailing List Subject: Re: memory range R/W triggered breakpoints in kernel ? Message-ID: <20060305233202.GD20768@kvack.org> References: <20060305231654.GB20768@kvack.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 850 Lines: 19 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: . - 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/