Re: [RFA] OSF/1 - "next" over prologueless function call

[Joel Brobecker <brobecker@gnat.com>]

> 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