Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfa] gdbserver multiple register set issue: PBUFSIZ
Date: Thu, 08 May 2008 20:33:00 -0000	[thread overview]
Message-ID: <20080508185751.GA31519@caradoc.them.org> (raw)
In-Reply-To: <200805081828.m48ISqlb004187@d12av02.megacenter.de.ibm.com>

On Thu, May 08, 2008 at 08:28:52PM +0200, Ulrich Weigand wrote:
> I guess one way to fix this would be to have GDB issue another qSupported
> query after it re-attaches.  On the other hand, I'm not sure why this
> parameter is even limited by the register set size: when transferring
> memory or files (or other data like XML feature descriptions), allowing
> larger packet sizes would be helpful even on platforms where the register
> set is small.

Right.  It used to be that PBUFSIZ was much larger than any packet
we'd have reason to send except for g/G, but that's not true any more;
now there's bulk memory transfers and XML.

> As GDB limits the packet size to 16 KB anyway, I'd propose to simply
> always use 16 KB as PBUFSIZ as well.  The patch below implements this
> (together with a sanity check that register packets still fit).
> 
> Tested on powerpc-linux and powerpc64-linux in local gdbserver mode.
> 
> What do you think?   OK for mainline?

OK, thanks.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-05-08 18:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 19:52 Ulrich Weigand
2008-05-08 20:33 ` Daniel Jacobowitz [this message]
2008-05-09  1:23   ` Ulrich Weigand

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=20080508185751.GA31519@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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