Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: John Williams <jwilliams@itee.uq.edu.au>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdbserver version quandry
Date: Thu, 06 Nov 2003 00:50:00 -0000	[thread overview]
Message-ID: <3FA99FA2.2010600@itee.uq.edu.au> (raw)
In-Reply-To: <20031106003935.GA12798@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Thu, Nov 06, 2003 at 10:50:00AM +1000, John Williams wrote:
> 
>>Hi folks,
>>
>>I have recently completed a port of uClinux to the Xilinx Microblaze 
>>soft-processor architecture.
>>
>>http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux.
>>
>>I am now investigating providing gdbserver support for this architecture.
> 
> If your gdb 5.0 port supports remote debugging at all, then probably
> easiest is to take the most recent version of gdbserver and work from
> that.  Then adapt it to speak to your older client.  Not much should be
> required.

Yes - microblaze gdb 5.0 does supoprt remote debugging.  Xilinx never 
intended to support (uC)linux, so they wrote their own gdbserver-type 
program to run on the host, which then communicates with a stub on the 
target via a proprietary serial interface.

So then, the question becomes:  is there any info online about providing 
new arch support for gdb/gdbserver?

Also looking at gdbserver version strings in the Makefiles - I see that 
gdbserver versions don't track gdb versions.  In both the gdb5.0 and 
gdb5.1 distributions, the gdbserver version string is 4.12.3...   ???

Thanks,

John


  reply	other threads:[~2003-11-06  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06  0:29 John Williams
2003-11-06  0:39 ` Daniel Jacobowitz
2003-11-06  0:50   ` John Williams [this message]
2003-11-06 15:04     ` Daniel Jacobowitz
2003-11-06 21:29       ` John Williams

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=3FA99FA2.2010600@itee.uq.edu.au \
    --to=jwilliams@itee.uq.edu.au \
    --cc=drow@mvista.com \
    --cc=gdb@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