From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 10584 invoked by alias); 27 Jan 2008 15:38:36 -0000 Received: (qmail 10572 invoked by uid 22791); 27 Jan 2008 15:38:35 -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; Sun, 27 Jan 2008 15:38:05 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 084D098118; Sun, 27 Jan 2008 15:38:04 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id C655C9810C; Sun, 27 Jan 2008 15:38:03 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.68) (envelope-from ) id 1JJ9a6-0000vQ-Po; Sun, 27 Jan 2008 10:38:02 -0500 Date: Sun, 27 Jan 2008 15:38:00 -0000 From: Daniel Jacobowitz To: Mark Kettenis Cc: cseo@linux.vnet.ibm.com, jimb@codesourcery.com, gdb@sourceware.org Subject: Re: expand-symtabs.exp Message-ID: <20080127153802.GA3449@caradoc.them.org> Mail-Followup-To: Mark Kettenis , cseo@linux.vnet.ibm.com, jimb@codesourcery.com, gdb@sourceware.org References: <200801271528.m0RFSMo6032355@brahms.sibelius.xs4all.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200801271528.m0RFSMo6032355@brahms.sibelius.xs4all.nl> User-Agent: Mutt/1.5.17 (2007-12-11) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2008-01/txt/msg00277.txt.bz2 On Sun, Jan 27, 2008 at 04:28:22PM +0100, Mark Kettenis wrote: > The new expand-psymtabs.exp consistently fails on all systems I try it > on with something like: > > > (gdb) break 32 > No line 32 in file "../../../../src/gdb/gdb/testsuite/gdb.base/expand-psymtabs.c". > (gdb) FAIL: gdb.base/expand-psymtabs.exp: Expand psymtabs > > > Looking at the source code for this test, GDB's respnse here is quite > reasonable, since line 32 is the line withe the comment /* Break here > */ in the code fragment below: GDB's historical behavior in that case is to set a breakpoint on the next line, and there ought to be code for the next line (the epilogue). It looks like you're hitting the bug the testcase was written for. Does break 32 work with -readnow? FWIW, it passed for me (Debian x86_64). http://sourceware.org/ml/gdb-patches/2007-10/msg00456.html -- Daniel Jacobowitz CodeSourcery