From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7172 invoked by alias); 2 Dec 2003 07:21:16 -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 7125 invoked from network); 2 Dec 2003 07:21:14 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sources.redhat.com with SMTP; 2 Dec 2003 07:21:14 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 8218447D5B; Mon, 1 Dec 2003 23:21:13 -0800 (PST) Date: Tue, 02 Dec 2003 07:21:00 -0000 From: Joel Brobecker To: Richard Henderson Cc: gdb-patches@sources.redhat.com Subject: Re: [RFA] OSF/1 - "next" over prologueless function call Message-ID: <20031202072113.GS22119@gnat.com> References: <20031202042646.GW1186@gnat.com> <20031202063532.GC31561@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031202063532.GC31561@redhat.com> User-Agent: Mutt/1.4i X-SW-Source: 2003-12/txt/msg00043.txt.bz2 > Is there any chance we could get hold of the symbol associated with > this function start? I don't know. I think that information is lost after we've read in the symbol table. However... > On ELF detecting this condition can be > streamlined to > > sym->st_other & STO_ALPHA_STD_GPLOAD == STO_ALPHA_STD_GPLOAD > > or from bfd, elf_link_hash_entry.other, though I don't remember off > the top of my head how to get at the elf hash entry from asymbol. ... I see some target-specific code uses a grab-bag field of the minimal_symbol structure to store some target-specific information (field "info"). I don't particularly fancy typeless fields like this, but, just thinking aloud, we could add a new fields holding some flags which would be defined in gdb in an manor independent of the target. Also: OSF/1 uses ECOFF. Fortunately, the information seems to be there too. If you look at a Procedure Descritptor Table Entry, one finds that it has 2 fields named: "gp_prologue" (byte size of the gp prologue), and "gp_used" (flag set if the procedure uses gp). I am not completely clear about the exact significance of the first field, but it's a promising start. So that's indeed another approach that the maintainers can consider, I would say. -- Joel