From owner-freebsd-hackers Fri Sep 21 13: 3:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B114837B40B for ; Fri, 21 Sep 2001 13:03:41 -0700 (PDT) Received: from onyx (onyx.cs.binghamton.edu [128.226.140.171]) by bingnet2.cc.binghamton.edu (8.11.4/8.11.4) with ESMTP id f8LK3eo10511 for ; Fri, 21 Sep 2001 16:03:40 -0400 (EDT) Date: Fri, 21 Sep 2001 16:03:25 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@onyx To: freebsd-hackers@freebsd.org Subject: Kernel module debugging help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am using gdb a lot recently and find out that most of the bugs are memory related. I am wondering how to set up a hardware breakpoint which is triggered whenever a memory address is written again. I have no experience with this subject. Another minor question is how to set a static variable inside a function. Acoording the GDB manual, I should be able to say: (gdb) set function_name::my_static_variable = somevalue But it does not work. I am using 4.3-release on a PC. Thanks for your help. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message