From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20828 invoked by alias); 12 Aug 2003 15:11:26 -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 20806 invoked from network); 12 Aug 2003 15:11:21 -0000 Received: from unknown (HELO miranda.se.axis.com) (212.209.10.215) by sources.redhat.com with SMTP; 12 Aug 2003 15:11:21 -0000 Received: from axis.com (ironmaiden.se.axis.com [10.13.8.120]) by miranda.se.axis.com (8.12.8p1/8.12.8/Debian-2woody1) with ESMTP id h7CFBJrG018493 for ; Tue, 12 Aug 2003 17:11:19 +0200 Message-ID: <3F390397.4010908@axis.com> Date: Tue, 12 Aug 2003 15:11:00 -0000 From: Orjan Friberg Organization: Axis Communications User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030312 X-Accept-Language: en MIME-Version: 1.0 To: gdb-patches@sources.redhat.com Subject: Re: CRIS port; frame cleanup crash References: <3F379A74.4080508@axis.com> In-Reply-To: <3F379A74.4080508@axis.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00192.txt.bz2 Orjan Friberg wrote: > After a long overdue update of my gdb cvs tree, I found that something > broke late March/early April. I don't quite understand what goes on, > but it seems to happen the first time a frame allocated by > deprecated_frame_xmalloc_with_cleanup is freed by do_cleanups (which > happens in cris_skip_prologue_main). gdb segfaults on a call to free > with a pointer to that frame. I hacked around that particular failure by not allocating a frame, and simply relying on symbol information. With that out of the way, I'm able to run the testsuite, albeit with some more FAILs than stock a gdb 5.3. However, poking around in all the stuff that has been deprecated, I'm sort of at a loss as to where to start. Replacing the deprecated function/macros one at a time doesn't look feasible, since a lot of functionality is replaced by the same functions (push_dummy_code/push_dummy_call for example). Is there a preferred way of doing it, or is it just a matter of diving right into it? I'd prefer to do it in a structured way to be able to catch when things start to break. I see there are a couple of targets that have made the transition (d10v and m68hc11 for example), so that should provide some help. Also, is there any documentation for the frame handling machinery that I didn't find? I checked the archives, and read a bunch of Andrew Cagney's posts related to this, but couldn't really get the big picture from that. (The Internals manual has only a brief mention of frames in section 3.1.) Thanks for any help. -- Orjan Friberg Axis Communications