From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14173 invoked by alias); 26 Jan 2003 10:50:58 -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 14166 invoked from network); 26 Jan 2003 10:50:56 -0000 Received: from unknown (HELO hotmail.com) (64.4.9.148) by 172.16.49.205 with SMTP; 26 Jan 2003 10:50:56 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 26 Jan 2003 02:50:56 -0800 Received: from 81.68.32.138 by lw9fd.law9.hotmail.msn.com with HTTP; Sun, 26 Jan 2003 10:50:55 GMT X-Originating-IP: [81.68.32.138] From: "Jan Hoogerbrugge" To: drow@mvista.com Cc: gdb@sources.redhat.com Bcc: Subject: Re: two gdb porting questions Date: Sun, 26 Jan 2003 10:50:00 -0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 26 Jan 2003 10:50:56.0222 (UTC) FILETIME=[CDD187E0:01C2C528] X-SW-Source: 2003-01/txt/msg00418.txt.bz2 >From: Daniel Jacobowitz > > * I want to use stabs to pass frame information from my compiler to > > gdb. Which stab number(s) should I use for this? How do I get this > > information in my xxx-tdep.c given the start address of the > > function? (I use ELF in the case that matters) > >Is it absolutely necessary that you use stabs? There are clean ways to >express this information in DWARF-2, and if you're using ELF, there's >really no excuse. My compiler (which is not gcc) happens to generate stabs. So I have to do it with stabs. Currently the compiler misuses a N_ROSYM to pass frame info to its debugger. However, gdb does not like this. Are there other targets where a stab is used for frame information? The instruction format of the debug target is so complex that decoding the prologue is not a real option. Cheers, Jan _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963