Re: Re : Debugging v8plus binaries on solaris

[Mark Kettenis <mark dot kettenis at xs4all dot nl>]

> Date: Fri, 17 Feb 2006 14:51:31 -0800
> From: Olatunji Ruwase <Olatunji.Ruwase@Sun.COM>

Sorry, I spent most of the week in bed/on the couch in front of the
telly with a bad flu :(.  I had a first glance at it last week, but
I'm afraid it needs a bit more work.

For one thing, I think it's important to split the generic v8plus
target support out from the Solaris v8plus native support.  And
concentrate on the target support first.  The seperation is mostly
already there (*-tdep.c versus *-nat.c), but some of the Solaris
native "weirdness" (which I realize is necessary for backwards
compatibility) has crept into the target support.

Looking from an OS agnostic point onto the v8plus support code, I
really think v8plus should be a seperate architecture much in the same
way existing 64-bit support is seperate from the 32-bit support.  Of
course this v8plus architecture should reuse as much code from the
existing 32-bit code as possible, and if the 32-bit code can be
generalized to work for v8plus as well, that's great, but I think
constructs like

  if (sparc_v8plus)
    {
      ...
    }
  else
    {
      ...
    }

should be avoided.  I also think the xregset stuff should be moved
into Solaris-specific files, perhaps even into Solaris-specofic
*-nat.c files.  This depends a bit on how v8plus core dumps look.  If
they have the xregset stuff too, the code should probably be moved to
sparc-sol2-tdep.c or sparc64-sol2-tdep.c.

Is the v8plus ABI documented somewhere?

Mark