From owner-freebsd-questions Mon Jun 16 12:59:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA26761 for questions-outgoing; Mon, 16 Jun 1997 12:59:09 -0700 (PDT) Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA26750 for ; Mon, 16 Jun 1997 12:59:02 -0700 (PDT) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id PAA21860 for ; Mon, 16 Jun 1997 15:57:54 -0400 (EDT) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.8.5/8.8.5) with ESMTP id PAA00311 for ; Mon, 16 Jun 1997 15:58:30 -0400 (EDT) Message-Id: <199706161958.PAA00311@bmcgover-pc.cisco.com> To: questions@freebsd.org Subject: Kernel debugging question... Date: Mon, 16 Jun 1997 15:58:30 -0400 From: Brian McGovern Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is there a way to get the kernel debugger (I'll be using it as a remote debug, with gdb/ddd as a front end) to stop executing when a particular memory address gets modified? I'm having problems with a pointer in shared memory (between the OS and hardware) getting changed unexpectedly. I suspect its the firmware on the card, but I want to see if there is a way I can verify that its not the kernel itself. I've checked the code that IS supposed to manipluate it, and it works fine. I'm curious to see if its some other pointer math that may be screwed up thats accidently stomping on it. Thanks. -Brian