Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Nathan Sidwell <nathan@codesourcery.com>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: gdb@sources.redhat.com,  jr.peulve@wanadoo.fr
Subject: Re: gdbserver for m68k-uclinux
Date: Tue, 09 May 2006 14:13:00 -0000	[thread overview]
Message-ID: <44609711.4030504@codesourcery.com> (raw)
In-Reply-To: <20060509123836.GB2147@nevyn.them.org>

Daniel Jacobowitz wrote:
> On Mon, May 08, 2006 at 03:15:20PM +0100, Nathan Sidwell wrote:
> 
>>This patch implements the necessary qOffsets logic tso that a uclinux 
>>hosted gdbserver can tell a remote gdb what the text & data offsets are.  
>>It also uses vfork on such systems.
>>
>>This implementation clearly separates the gdb protocol pieces of qOffsets 
>>from the system specific pieces of determining the offsets.  The original 
>>diff I found on the uclinux site did not have such a separation, I used 
>>that implementation for inspiration.
>>
>>Tested on a m5208evb hosted uclinux system.
>>
>>ok?
> 
> 
> Yes, this is OK.  Thanks.

> 
> Is LDFLAGS really necessary here?  I thought the toolchain took care of
> it.

I think at the point I developed this patch, the compiler didn't take care of it 
:)  I can remove it.

nathan

-- 
Nathan Sidwell    ::   http://www.codesourcery.com   ::         CodeSourcery
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


      reply	other threads:[~2006-05-09 13:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-08 16:57 Nathan Sidwell
2006-05-09 11:58 ` Jean-Rene Peulve
2006-05-09 12:19   ` Nathan Sidwell
2006-05-09 12:34     ` Jean-Rene Peulve
2006-05-09 12:39       ` Daniel Jacobowitz
2006-05-09 13:20 ` Daniel Jacobowitz
2006-05-09 14:13   ` Nathan Sidwell [this message]

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=44609711.4030504@codesourcery.com \
    --to=nathan@codesourcery.com \
    --cc=dan@codesourcery.com \
    --cc=gdb@sources.redhat.com \
    --cc=jr.peulve@wanadoo.fr \
    /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