From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Olatunji.Ruwase@Sun.COM
Cc: gdb-patches@sources.redhat.com
Subject: Re: Re : Debugging v8plus binaries on solaris
Date: Fri, 17 Feb 2006 23:31:00 -0000 [thread overview]
Message-ID: <200602172331.k1HNVj1L030314@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <43F65373.5020805@Sun.COM> (message from Olatunji Ruwase on Fri, 17 Feb 2006 14:51:31 -0800)
> 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
next prev parent reply other threads:[~2006-02-17 23:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 20:12 Olatunji Ruwase
2006-02-17 22:52 ` Olatunji Ruwase
2006-02-17 23:31 ` Mark Kettenis [this message]
2006-02-22 18:24 ` Olatunji Ruwase
2006-03-03 19:46 ` Olatunji Ruwase
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200602172331.k1HNVj1L030314@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=Olatunji.Ruwase@Sun.COM \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox