Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751256AbVKAVa1 (ORCPT ); Tue, 1 Nov 2005 16:30:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751260AbVKAVa1 (ORCPT ); Tue, 1 Nov 2005 16:30:27 -0500 Received: from iolanthe.rowland.org ([192.131.102.54]:40608 "HELO iolanthe.rowland.org") by vger.kernel.org with SMTP id S1751256AbVKAVa1 (ORCPT ); Tue, 1 Nov 2005 16:30:27 -0500 Date: Tue, 1 Nov 2005 16:30:26 -0500 (EST) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Kernel development list Subject: Setting kernel data breakpoints on x86 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 20 I'm trying to debug a rather difficult data-overwriting problem, and it would be a big help to be able to use a data breakpoint. Is there any easy way of doing this? I'd prefer not to use a kernel debugger, because the address of the breakpoint and the time when it's needed are determined dynamically. Does anybody have a little lightweight procedure for setting one of the x86's debug registers to point to a particular location in kernel memory space? I don't care if the whole system crashes when the debug exception occurs, just so long as I can get a stack trace and find out where the overwrite comes from. Alan Stern - 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/