Date: Sun, 18 Nov 2001 11:00:10 -0500 From: Brian Dean <bsd@bsdhome.com> To: Matthew Emmerton <matt@gsicomp.on.ca> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Does DDB's watch feature actually work? Message-ID: <20011118110010.A90083@neutrino.bsdhome.com> In-Reply-To: <048401c16fe7$7bf13b60$1200a8c0@gsicomp.on.ca>; from matt@gsicomp.on.ca on Sat, Nov 17, 2001 at 11:14:10PM -0500 References: <048401c16fe7$7bf13b60$1200a8c0@gsicomp.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Nov 17, 2001 at 11:14:10PM -0500, Matthew Emmerton wrote: > So, I decided to learn how to use DDB, and set a watch on the data element > that's getting blown away. The problem is, once I've got a watch in place, > the system traps (page fault) at the strangest locations in the networking > code -- %eip is nowhere near any code that modifies the data that I'm > watching. You can try 'hwatch' if you are running a reasonably recent -current or -stable to safely watch memory in the kernel (non-SMP). As for taking the trap within code you didn't expect, this can happen especially when the watch point is a stack address. Stack address watch points may be hit many times by other non-related functions as call frames are created and destroyed via normal execution. You can minimize this by only enabling the watch point while you are within the frame in question (sometimes not an easy task). -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011118110010.A90083>