From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14437 invoked by alias); 23 Feb 2004 06:26:41 -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 14423 invoked from network); 23 Feb 2004 06:26:39 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 23 Feb 2004 06:26:39 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu-dmz.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id i1N6Qcb18897 for ; Mon, 23 Feb 2004 01:26:38 -0500 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i1N6QbM28942; Mon, 23 Feb 2004 01:26:37 -0500 Received: from 192.168.1.129 (vpn50-2.rdu.redhat.com [172.16.50.2]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id i1N6QZX24806; Sun, 22 Feb 2004 22:26:35 -0800 From: Fred Fish Reply-To: fnf@redhat.com To: mec.gnu@mindspring.com (Michael Elizabeth Chastain), fnf@redhat.com Subject: Re: [RFA] Fix gdb.base/gdb1250.exp to work when abort() is in a shared library Date: Mon, 23 Feb 2004 06:26:00 -0000 User-Agent: KMail/1.5.4 Cc: gdb-patches@sources.redhat.com References: <20040223060451.25A2C4B104@berman.michael-chastain.com> In-Reply-To: <20040223060451.25A2C4B104@berman.michael-chastain.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402222326.33562.fnf@ninemoons.com> X-SW-Source: 2004-02/txt/msg00631.txt.bz2 On Sunday 22 February 2004 23:04, Michael Elizabeth Chastain wrote: > On native i686-pc-linux-gnu, this used to work and then stopped > working with a PLT optimization in binutils HEAD. Thanks for the history on why this doesn't currently work. Most of my shared library work with gdb was from way back in the days when I'm pretty sure that you couldn't set breakpoints on symbols in shared libraries that had not yet been loaded, but perhaps I'm misremembering. Perhaps it would make sense to go ahead and install this change and then have a separate test that specifically checks that gdb can set a breakpoint on symbols expected to be in a shared library. -Fred