From: Daniel Jacobowitz <dmj+@andrew.cmu.edu>
To: Andrew Cagney <ac131313@cygnus.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] gdbserver 1/n - PBUFSIZ
Date: Thu, 19 Jul 2001 16:16:00 -0000 [thread overview]
Message-ID: <20010719161609.B30475@nevyn.them.org> (raw)
In-Reply-To: <20010719132118.A23973@nevyn.them.org>
On Thu, Jul 19, 2001 at 01:21:18PM -0700, Daniel Jacobowitz wrote:
> > > Here's the first bit. PBUFSIZ is used as an array initializer, but defined
> > > in terms of REGISTER_BYTES - which might not be a constant, and which I'd
> > > rather hide anyway. Later on, the design I'm hashing out for gdbserver's
> > > register cache will make it very easy to find the maximum value of
> > > REGISTER_BYTES, and we can make PBUFSIZ flexible again; for now, I made it
> > > "big enough".
> >
> >
> > If I'm correct above, why not just ask your backend how big it thinks
> > that register buffer is (via a function call). For some targets it
> > looks like it is just (sizeof (inferior_registers) + sizeof
> > (inferior_fp_registers)) for others it is a little bit more tricky but
> > nothing more.
>
> Well, the other issue is that it's currently assumed to be a constant.
> It's used for, e.g., an array at the top of main(). I could make it a
> variable and change all the arrays to alloca(), I suppose, but I'm not
> thrilled with that either.
[How -do- you manage to reply to one of my messages with the subject
and References: of another? :)]
Would you prefer I make PBUFSIZ non-constant and change the arrays to
alloca(), or simply make it a large constant? Something's got to give
:)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-07-19 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 11:36 Daniel Jacobowitz
2001-07-19 13:14 ` Andrew Cagney
2001-07-19 13:21 ` Daniel Jacobowitz
[not found] ` <3B575B8F.4050407@cygnus.com>
2001-07-19 16:12 ` Daniel Jacobowitz
2001-07-19 16:16 ` Daniel Jacobowitz [this message]
2001-07-20 16:54 ` Andrew Cagney
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=20010719161609.B30475@nevyn.them.org \
--to=dmj+@andrew.cmu.edu \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@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