From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16285 invoked by alias); 28 Sep 2005 14:59:21 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16268 invoked by uid 22791); 28 Sep 2005 14:59:15 -0000 Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Wed, 28 Sep 2005 14:59:15 +0000 Received: from drow by nevyn.them.org with local (Exim 4.52) id 1EKdO5-0002Rw-Tp; Wed, 28 Sep 2005 10:58:26 -0400 Date: Wed, 28 Sep 2005 14:59:00 -0000 From: Daniel Jacobowitz To: Andreas Schwab Cc: gdb-patches@sources.redhat.com Subject: Re: PR threads/2015: Fix adjust_pc_after_break for thread debugging Message-ID: <20050928145825.GA8872@nevyn.them.org> Mail-Followup-To: Andreas Schwab , gdb-patches@sources.redhat.com References: <20050927221952.GA22753@nevyn.them.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i X-SW-Source: 2005-09/txt/msg00274.txt.bz2 On Wed, Sep 28, 2005 at 12:57:16AM +0200, Andreas Schwab wrote: > Daniel Jacobowitz writes: > > > Which test failures are these? i.e. why doesn't anyone else see this > > when they run the testsuite? > > I've somehow lost the log files and had to rerun the testsuite, and now I > no longer see any difference in the test results. > > > Offhand I'd be suspicious that this helped - some other thread probably > > needs its PC adjusted and now may not be. > > The patch will never result in less adjustments, because the other arm of > the conditional will do the adjustment anyway if a breakpoint exists at > the current PC. Note that prev_pc is also part of the thread context and > may be wrong for the current thread as well. Can you describe whatever testcase prompted you to make this change? Is there some way we can reproduce the situation? I've been looking this morning at a (probably unrelated) bug which would probably vanish if this patch were applied, but which was really triggered by an uninitialized variable in infrun. More to come once I've tested. -- Daniel Jacobowitz CodeSourcery, LLC