From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22138 invoked by alias); 22 Sep 2004 14:01:19 -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 22062 invoked from network); 22 Sep 2004 14:01:13 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 22 Sep 2004 14:01:13 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.10) with ESMTP id i8ME1DUo013497 for ; Wed, 22 Sep 2004 10:01:13 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i8ME17r06567; Wed, 22 Sep 2004 10:01:07 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 6111E28D2; Wed, 22 Sep 2004 09:58:51 -0400 (EDT) Message-ID: <4151851B.1040100@gnu.org> Date: Wed, 22 Sep 2004 14:01:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040831 MIME-Version: 1.0 To: pgilliam@us.ibm.com Cc: gdb-patches@sources.redhat.com, Michael Chastain Subject: Re: [PATCH] Fixes testsuit/gdb.base/annota1.exp References: <200409211441.33901.pgilliam@us.ibm.com> In-Reply-To: <200409211441.33901.pgilliam@us.ibm.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-09/txt/msg00353.txt.bz2 > On powerpc64--linux, annota1.exp has two problems: > > 1) A breakpoint in a shared object may be 'delayed'. This changes GDB's > responce: both when the breakpoint is set and when it is hit. I'm not sure what you mean. On i386 GNU/Linux, annota1.exp gets zero fails so this would suggest some sort of ISA specific bug? I see this lets GDB accept the ``warning: adjusting breakpoint'' message. I'm wondering if GDB should even emit the warning - it and the descriptor are very much integral parts of the ABI - and hence should be trying to always display the descriptor symbol and code address (and not display the dot symbol). What's going to happen when 64-bit PPC stops emiting those dot symbols? > 2) Due to a bug (I which I knew the number), GDB 'skids' past the top-of-stack > when doing a backtrace. This causes two extra and severial garbage stack > frames to be displayed, eventually getting an error. You mean backtracing past main - that code was recently rewritten. However, there's apparently no test case for the feature, perhaphs it it should first be added and fixed?. Anyway, I don't think we should be passing a broken backtrace. Andrew > I have attached three patches: seperate patches for these two problems and one > patch that fixes them both. I have also attached test logs so you can see > what's up. > > Ok to commit? (which one(s)?) > > -=# Paul #=- > > PS: I thought the 'skidding past top-of-stack' problem was fixed. But it > doesn't seem to be in cvs-main as of last week sometime.