From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7252 invoked by alias); 13 Aug 2003 23:35:47 -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 7245 invoked from network); 13 Aug 2003 23:35:47 -0000 Received: from unknown (HELO frothingslosh.sfbay.redhat.com) (66.187.237.200) by sources.redhat.com with SMTP; 13 Aug 2003 23:35:47 -0000 Received: from frothingslosh.sfbay.redhat.com (localhost.localdomain [127.0.0.1]) by frothingslosh.sfbay.redhat.com (8.12.8/8.12.8) with ESMTP id h7DNZh2m026192; Wed, 13 Aug 2003 16:35:43 -0700 Received: (from rth@localhost) by frothingslosh.sfbay.redhat.com (8.12.8/8.12.8/Submit) id h7DNZg0t026190; Wed, 13 Aug 2003 16:35:42 -0700 X-Authentication-Warning: frothingslosh.sfbay.redhat.com: rth set sender to rth@redhat.com using -f Date: Wed, 13 Aug 2003 23:35:00 -0000 From: Richard Henderson To: Andrew Cagney Cc: Michal Ludvig , Daniel Jacobowitz , gdb Subject: Re: [testsuite & dwarf2] How to handle store.exp failure on AMD64? Message-ID: <20030813233542.GA26172@redhat.com> References: <20030807135035.GA28000@nevyn.them.org> <3F326928.3020502@redhat.com> <20030807150201.GA29511@nevyn.them.org> <3F3275EC.3000702@redhat.com> <3F32C75D.2010007@suse.cz> <3F39B678.70409@redhat.com> <20030813045405.GB11912@redhat.com> <3F3A4DAD.7000702@redhat.com> <20030813165034.GA12234@redhat.com> <3F3A8203.5060102@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F3A8203.5060102@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-08/txt/msg00142.txt.bz2 > >Moreover, the algorithm I suggested that you use -- assume saved -- > >is also completely independant of the ABI, so its' not like GDB > >needs to hard code ABI specific information either. > > It doesn't work in general. > On a register window machine, it could use a fairly complex starting > state vis: > globals: same > locals: where saved on stack > input: undefined > output: in input > (register windows give me a headache so don't assume this one is correct :-) This has to be handled with the same magic that handles register windows in the first place. I.e. DW_CFA_GNU_window_save. Dwarf2 doesn't handle windows itself at all. You could also do it with explicit dw2 operations, but that's no different than a non-windowed system than starts with all DW_CFA_same_value and adds DW_CFA_undefined, DW_CFA_register and DW_CFA_offset notes as needed. > [perhaphs I should have cross posted this with dwarf2 :-)] Probably. r~