Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Olatunji Ruwase <Olatunji.Ruwase@Sun.COM>
To: gdb@sourceware.org
Subject: Re: Debugging on v8plus
Date: Tue, 24 Jan 2006 19:36:00 -0000	[thread overview]
Message-ID: <43D671C7.3090101@Sun.COM> (raw)
In-Reply-To: <20060124181918.GA22064@nevyn.them.org>



Daniel Jacobowitz wrote On 01/24/06 10:19,:
> On Tue, Jan 24, 2006 at 10:10:39AM -0800, Olatunji Ruwase wrote:
> 
>>
>>Daniel Jacobowitz wrote On 01/24/06 08:29,:
>>
>>>On Tue, Jan 24, 2006 at 08:15:49AM -0800, Olatunji Ruwase wrote:
>>>
>>>
>>>>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 ?. Or is there
>>>>some other technical reason ?.
>>>>In other words will a patch for this support be accepted into gdb ?.
>>>
>>>
>>>Presumably it would be, if someone was interested in implementing it
>>>(along with filing an FSF copyright assignment).
>>>
>>
>>Daniel,
>>
>>I m interested in doing this work. Can I contact you directly with
>>questions I might while doing this ?
> 
> 
> No, please don't contact developers off-list - use the mailing list,
> that's what it's for.  I don't know much about either SPARC or Solaris.
> 
Will do.

Thanks.
tunji


  reply	other threads:[~2006-01-24 18:28 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 [this message]
2006-01-24 20:18 ` Mark Kettenis
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=43D671C7.3090101@Sun.COM \
    --to=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