From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10802 invoked by alias); 17 Apr 2003 20:10:01 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10795 invoked from network); 17 Apr 2003 20:10:00 -0000 Received: from unknown (HELO morte.jpl.nasa.gov) (137.78.15.44) by sources.redhat.com with SMTP; 17 Apr 2003 20:10:00 -0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by morte.jpl.nasa.gov (Postfix) with ESMTP id 370A9404C92 for ; Thu, 17 Apr 2003 13:10:00 -0700 (PDT) Subject: Setting watchpoints From: Al Niessner To: gdb@sources.redhat.com Content-Type: text/plain Organization: Jet Propulsion Laboratory Message-Id: <1050610199.24880.20.camel@morte.jpl.nasa.gov> Mime-Version: 1.0 Date: Thu, 17 Apr 2003 20:10:00 -0000 Content-Transfer-Encoding: 7bit X-SW-Source: 2003-04/txt/msg00199.txt.bz2 Platform information: OS: Linux Kernel: 2.4.19 gcc/g++: 3.2.2 gdb: 5.3 threads: 1 -- single threaded application How do I set a watch point so that the debugger halts when memory at a specific address is changed? There is no easy to define variable that I can latch onto, but I do know its address. When I set a watch point to this address -- 'watch 0x8559ff4' or 'watch *0x8559ff4' -- gdb just sails by this memory being changed. If I set a conditional break point just prior to the segmentation fault I can see the change and so can gdb it just does not sense it with the watch. So, what am I doing wrong and how do I get gdb to monitor a memory location and halt when it changes? I have already searched the web (google) and did not find any solutions there. -- Al Niessner Jet Propulsion Laboratory All opinions stated above are mine and do not necessarily reflect those of JPL or NASA. ---- | dS | >= 0 ----