From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11806 invoked by alias); 25 Aug 2010 20:50:34 -0000 Received: (qmail 11790 invoked by uid 48); 25 Aug 2010 20:50:34 -0000 Date: Wed, 25 Aug 2010 20:50:00 -0000 Message-ID: <20100825205034.11789.qmail@sourceware.org> From: "pedro at codesourcery dot com" To: gdb-prs@sourceware.org In-Reply-To: <20090824231914.10557.ppluzhnikov@google.com> References: <20090824231914.10557.ppluzhnikov@google.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug breakpoints/10557] HW watchpoints silently degrade into SW ones X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q3/txt/msg00305.txt.bz2 ------- Additional Comments From pedro at codesourcery dot com 2010-08-25 20:50 ------- I don't see evidence of degeneration into single-stepping: > infrun: TARGET_WAITKIND_STOPPED > infrun: stop_pc = 0x400507 > infrun: stopped by watchpoint > infrun: stopped data address = 0x7fffffffd9f0 > infrun: no stepping, continue > infrun: resume (step=0, signal=0), trap_expected=0 It appears to me the target is continuously reporting that something is writing to the address you are watching, but, if the watched expression evaluates to the same at each of those, then gdb will silently resume the inferior again. This is the nature of write watchpoints. Try an access watchpoint instead (awatch). Your testcase looks bogus to me. The heap memory address you are watching in the new run of the program is most likely being used for something else during program startup? -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |WAITING http://sourceware.org/bugzilla/show_bug.cgi?id=10557 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.