From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7156 invoked by alias); 3 Feb 2003 18:15:33 -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 7149 invoked from network); 3 Feb 2003 18:15:33 -0000 Received: from unknown (HELO jackfruit.Stanford.EDU) (171.64.38.136) by 172.16.49.205 with SMTP; 3 Feb 2003 18:15:33 -0000 Received: (from carlton@localhost) by jackfruit.Stanford.EDU (8.11.6/8.11.6) id h13IFK823324; Mon, 3 Feb 2003 10:15:20 -0800 X-Authentication-Warning: jackfruit.Stanford.EDU: carlton set sender to carlton@math.stanford.edu using -f To: Andrew Cagney Cc: Jason Molenda , gdb-patches@sources.redhat.com, jjohnstn@redhat.com Subject: Re: PATCH RFA: Fix MI stack frame output for synthetic frames References: <20021108142248.A65720@molenda.com> <3DCC3CEE.5040902@redhat.com> <20021109004723.A20334@molenda.com> <3E3CB218.1020706@redhat.com> From: David Carlton Date: Mon, 03 Feb 2003 18:15:00 -0000 In-Reply-To: <3E3CB218.1020706@redhat.com> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.4 (Common Lisp) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2003-02/txt/msg00069.txt.bz2 On Sun, 02 Feb 2003 00:52:24 -0500, Andrew Cagney said: >> [gdb/ChangeLog] >> 2002-11-09 Jason Molenda (jason-cl@molenda.com) >> * stack.c (print_frame_info_base): Output complete FRAME tuple >> for synthesized frames. >> [gdb/testsuite/ChangeLog] >> 2002-11-09 Jason Molenda (jason-cl@molenda.com) >> * gdb.mi/mi-syn-frame.exp: New tests for synthetic frames in >> stack backtraces. >> * gdb.mi/inferior-mischief.c: Part of same. >> > I've (finally ...) tested it and checked it in. (renamed > inferior-mischief.c to mi-syn-frame.c though - booring). > Passes fine on x86. I suspect other targets won't be so lucky. On i686-pc-linux-gnu/GCC3.1/DWARF2, I get the following: Running ./gdb.mi/mi-syn-frame.exp ... PASS: gdb.mi/mi-syn-frame.exp: breakpoint at main PASS: gdb.mi/mi-syn-frame.exp: mi runto main PASS: gdb.mi/mi-syn-frame.exp: 400-break-insert foo PASS: gdb.mi/mi-syn-frame.exp: call inferior's function with a breakpoint set in it PASS: gdb.mi/mi-syn-frame.exp: backtrace from inferior function stopped at bp, showing gdb dummy frame PASS: gdb.mi/mi-syn-frame.exp: 403-exec-continue PASS: gdb.mi/mi-syn-frame.exp: 404-stack-list-frames 0 0 PASS: gdb.mi/mi-syn-frame.exp: 405-break-insert subroutine PASS: gdb.mi/mi-syn-frame.exp: 406-data-evaluate-expression have_a_very_merry_interrupt() PASS: gdb.mi/mi-syn-frame.exp: 407-stack-list-frames FAIL: gdb.mi/mi-syn-frame.exp: 408-exec-continue FAIL: gdb.mi/mi-syn-frame.exp: 409-stack-list-frames 0 0 FAIL: gdb.mi/mi-syn-frame.exp: call inferior function which raises exception FAIL: gdb.mi/mi-syn-frame.exp: backtrace from inferior function at exception I haven't investigated the failures at all. David Carlton carlton@math.stanford.edu