From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: PATCH: allocate namecopy on heap, not stack
Date: Fri, 29 Apr 2005 22:54:00 -0000 [thread overview]
Message-ID: <vt2wtqldwm5.fsf@zenia.home> (raw)
In-Reply-To: <20050429213922.GA9371@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> On Fri, Apr 29, 2005 at 04:35:35PM -0500, Jim Blandy wrote:
> >
> > Committed as obvious.
> >
> > 2005-04-28 Jim Blandy <jimb@redhat.com>
> >
> > * parse.c (namecopy): Change allocation conventions.
> > (namecopy_size): New variable.
> > (copy_name): Allocate namecopy using xrealloc, instead of assuming
> > it has adequate space allocated to it.
> > (parse_exp_1): Don't try to allocate space for namecopy here.
>
> What prompted ths change? Even "obvious" patches deserve an
> explanation.
Certainly --- did you see this?
+
+ /* A temporary buffer for identifiers, so we can null-terminate them.
+
+ We allocate this with xrealloc. parse_exp_1 used to allocate with
+ alloca, using the size of the whole expression as a conservative
+ estimate of the space needed. However, macro expansion can
+ introduce names longer than the original expression; there's no
+ practical way to know beforehand how large that might be. */
+ char *namecopy;
+ size_t namecopy_size;
next prev parent reply other threads:[~2005-04-29 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-29 21:38 Jim Blandy
2005-04-29 21:39 ` Daniel Jacobowitz
2005-04-29 22:54 ` Jim Blandy [this message]
2005-04-29 23:56 ` Daniel Jacobowitz
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=vt2wtqldwm5.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=drow@false.org \
--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