From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26754 invoked by alias); 17 Apr 2008 12:35:25 -0000 Received: (qmail 26746 invoked by uid 22791); 17 Apr 2008 12:35:25 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 17 Apr 2008 12:34:59 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 43CD0983D6 for ; Thu, 17 Apr 2008 12:34:57 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 2F451982C4 for ; Thu, 17 Apr 2008 12:34:57 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1JmTKJ-0006lK-RD for gdb-patches@sourceware.org; Thu, 17 Apr 2008 08:34:55 -0400 Date: Thu, 17 Apr 2008 14:53:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sourceware.org Subject: Re: [rfc, rfa/doc] Multi-threaded watchpoint improvements Message-ID: <20080417123455.GA25679@caradoc.them.org> Mail-Followup-To: gdb-patches@sourceware.org References: <20070916183949.GA23966@caradoc.them.org> <20071001002015.GA15835@caradoc.them.org> <20080416224910.GA3716@caradoc.them.org> <20080416231831.GB6274@caradoc.them.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2008-04/txt/msg00332.txt.bz2 On Thu, Apr 17, 2008 at 11:52:31AM +0200, Andreas Schwab wrote: > Looking closer, it is actually a kernel bug. PTRACE_GETSIGINFO is not > emulated for 32-bit processes, so that si_addr is set to the upper half > of the address, which is of course zero. Glad you could track that down. Yes, my patch made GDB less tolerant of targets which claim they can report the stopped data address, but actually fail. It will only report watchpoints when the target doesn't know what address has changed, or report a changed address that falls on a particular watchpoint. This lets us keep track of which thread hit each watchpoint. -- Daniel Jacobowitz CodeSourcery