From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-patches-return-20009-listarch-gdb-patches=sourceware.cygnus.com@sources.redhat.com>
Received: (qmail 24957 invoked by alias); 8 Nov 2002 23:56:19 -0000
Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:gdb-patches-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/gdb-patches/>
List-Post: <mailto:gdb-patches@sources.redhat.com>
List-Help: <mailto:gdb-patches-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: gdb-patches-owner@sources.redhat.com
Received: (qmail 24823 invoked from network); 8 Nov 2002 23:56:17 -0000
Received: from unknown (HELO localhost.redhat.com) (216.129.200.2)
  by sources.redhat.com with SMTP; 8 Nov 2002 23:56:17 -0000
Received: from redhat.com (localhost [127.0.0.1])
	by localhost.redhat.com (Postfix) with ESMTP
	id 974003FE4; Fri,  8 Nov 2002 18:56:06 -0500 (EST)
Message-ID: <3DCC4F16.7000500@redhat.com>
Date: Fri, 08 Nov 2002 15:56:00 -0000
From: Andrew Cagney <ac131313@redhat.com>
User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.0) Gecko/20020824
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: gdb-patches@sources.redhat.com, jjohnstn@redhat.com
Subject: Re: PATCH: Fix MI stack frame output for synthetic frames
References: <20021108142248.A65720@molenda.com> <3DCC3CEE.5040902@redhat.com> <20021108144623.A71229@molenda.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2002-11/txt/msg00265.txt.bz2

> On Fri, Nov 08, 2002 at 05:38:38PM -0500, Andrew Cagney wrote:
> 
> 
>> It should be possible to test the "<function called from gdb>" case. 
>> All the more main-stream architectures now use dummy-frames so any one 
>> of them can be used for the test.
>> 
>> Can you do that?
> 
> 
> OK, I'll write up an MI test case for this and re-post the whole
> patch a bit later (off to help a user just now :-).  I can also 
> test the signal handler frame one a la gdb.base/signals.exp easily
> enough.  

Thanks.

Just note that, unlike all that older code, you can now assume:

- the message always appears (if it doesn't its a bug in that 
architecture not using dummy-frames :-)
- the unwind stops at main (if it doesn't for your target yell and 
someone will fix it :-)

Much easier!
Andrew


> For the tests I added to the Apple gdb, I use the following C file
> to test various cases (the function bar() I used for verifying
> unwindonsignal was working correctly) in MI and CLI mode.