From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: Olatunji.Ruwase@Sun.COM
Cc: gdb@sourceware.org
Subject: Re: Debugging on v8plus
Date: Tue, 24 Jan 2006 20:18:00 -0000 [thread overview]
Message-ID: <200601241936.k0OJa0fW021986@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <43D652B5.5060302@Sun.COM> (message from Olatunji Ruwase on Tue, 24 Jan 2006 08:15:49 -0800)
> Date: Tue, 24 Jan 2006 08:15:49 -0800
> From: Olatunji Ruwase <Olatunji.Ruwase@Sun.COM>
>
> Hello,
>
> I imagine that this issue has been discussed in the past, but I ve been
> unable to find much information searching through the archives. So
> pardon me for asking, but I m curious as to why there is no gdb support
> for debugging v8plus applications (i.e 64 bit registers in a 32 bit
> environment). Is it because this isnt important to users ?.
I'm not aware of any people who develop such applications, let alone
people who have requested this feature.
> Or is there some other technical reason ?.
Not really except for the fact that it's a bit pointless to compicate
gdb with code thyat nobody uses. A possible technical reason would be
that it should be possible for gdb to recognize such v8plus binaries.
> In other words will a patch for this support be accepted into gdb ?.
If you think there are people who actually need this and the copyright
on the changes is assigned to the FSF, there's no reason for us not to
accept it.
Mark
next prev parent reply other threads:[~2006-01-24 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 16:42 Olatunji Ruwase
2006-01-24 18:11 ` Daniel Jacobowitz
2006-01-24 18:19 ` Olatunji Ruwase
2006-01-24 18:28 ` Daniel Jacobowitz
2006-01-24 19:36 ` Olatunji Ruwase
2006-01-24 20:18 ` Mark Kettenis [this message]
2006-01-26 23:31 ` 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=200601241936.k0OJa0fW021986@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=Olatunji.Ruwase@Sun.COM \
--cc=gdb@sourceware.org \
/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