From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28564 invoked by alias); 15 Jul 2003 16:20:16 -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 28557 invoked from network); 15 Jul 2003 16:20:15 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 15 Jul 2003 16:20:15 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id DD76A2B7B; Tue, 15 Jul 2003 12:20:14 -0400 (EDT) Message-ID: <3F1429BE.3040904@redhat.com> Date: Tue, 15 Jul 2003 16:20:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: gdb-patches@sources.redhat.com Subject: Re: [rfa/testsuite] gdb1250.exp, new test script References: <200307151613.h6FGDvnQ011927@duracef.shout.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-07/txt/msg00290.txt.bz2 > Rats, I said I would do this yesterday. Here it is: a new test script > for PR gdb/1250. > > http://sources.redhat.com/gdb/bugs/1250 > > This is the bug where gdb loses its marbles when backtracing through a > function which calls a noreturn function such as 'abort'. The calling > function has no epilog after the call to 'abort', so when gdb looks at > the frame for that function, gdb sees the first instruction of the > *next* function and uses information for that function instead. > > This happens in gdb.base/corefile.exp but I think it is nice to have a > specific test for it. > > I tested this on native i686-pc-linux-gnu with gdb HEAD, gcc 2.95.3 and > v3, dwarf-2 and stabs+. > > It PASSed with gcc 2.95.3 because gcc 2.95.3 does not optimize away the > epilog. I think that this is okay. The gdb user really just wants to > put breakpoints on things like 'abort' and 'exit' and have it work, and > if it works because the compiler is simple, that is okay. > > It KFAILed with all the gcc 3.3's that I used. > > I would like to commit this to HEAD, wait a few days or a week, and then > commit it to gdb_6_0-branch. > > OK to commit? Definitly, and thanks. Andrew