Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix gdbserver on ia64
Date: Tue, 25 Oct 2005 08:02:00 -0000	[thread overview]
Message-ID: <20051024235635.GA6864@nevyn.them.org> (raw)
In-Reply-To: <je8xwi1nr5.fsf@sykes.suse.de>

On Tue, Oct 25, 2005 at 01:47:10AM +0200, Andreas Schwab wrote:
> This patch makes gdbserver on ia64 a bit more useful:
> 
> - gdb assumes 462 registers, gdbserver 590 registers, causing a mismatch
>   on the 'g' packet
> - gdb assumes it can send/receive at most the size of a 'g' packet in one
>   'm' packet, gdbserver was assuming at most 2000 bytes.

Thanks!  These are fine.  Please get the copyright date in
linux-ia64-low.c too.

Do you know offhand if the NAT bits change is a recent change in gdb,
or if I got it wrong to begin with?  I don't know if I ever tested the
ia64 bits.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-10-24 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-24 23:56 Andreas Schwab
2005-10-25  8:02 ` Daniel Jacobowitz [this message]
2005-10-25 11:16   ` Andreas Schwab
2005-10-25 12:40     ` Andreas Schwab

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=20051024235635.GA6864@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=schwab@suse.de \
    /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