From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3862 invoked by alias); 26 Sep 2002 22:47:16 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 3853 invoked from network); 26 Sep 2002 22:47:13 -0000 Received: from unknown (HELO localhost.redhat.com) (216.138.202.10) by sources.redhat.com with SMTP; 26 Sep 2002 22:47:13 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id EAE8F3DC7 for ; Thu, 26 Sep 2002 18:47:11 -0400 (EDT) Message-ID: <3D938E6F.6090809@redhat.com> Date: Thu, 26 Sep 2002 15:47:00 -0000 From: Andrew Cagney 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: gdb@sources.redhat.com Subject: RFC: dummy.[hc] and ``struct dummy'' Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-09/txt/msg00462.txt.bz2 Hello, I'd like to float the idea of moving all the generic dummy frame code into a new file dummy.[hc]. Things like hand_function_call() would then use a ``struct dummy'' that contains the information for the dummy frame currently being constructed. That way the current global top-of-dummy stack assumption is removed. This should also make it simplier/easier to do things like make what is currently a single global dummy frame stack part of the ``thread_info'' object. (Figuring out why one would want to do this is left as an exercise for the reader. LiamS, GraceS and I stumbled across this think-o :-). Andrew