From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix PR 2506
Date: Tue, 21 Oct 2008 18:56:00 -0000 [thread overview]
Message-ID: <m3iqrl93uk.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200810211727.18574.pedro@codesourcery.com> (Pedro Alves's message of "Tue\, 21 Oct 2008 17\:27\:17 +0100")
Pedro> This crashes for me:
Pedro> print "foo" "bar" "boo"
Pedro> :-(
Thanks.
I added a new test case and fixed this problem.
I'm sending it back through the regression tester now.
Pedro> Also, these files don't use xmalloc/xfree. Instead, one writes
Pedro> malloc/free; they're sed'ed by the build system --- see the top of
Pedro> c-exp.y.
I made this change.
Two notes here: first, the Makefile doesn't actually s/free/xfree/ --
it only handles malloc and realloc. Funny. This should not really
matter in practice.
Second, ada-exp.y uses xmalloc once and p-exp.y uses xfree once, in
case anybody wants to clean that up.
I'll resubmit once the testing is finished.
Tom
next prev parent reply other threads:[~2008-10-21 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 1:56 Tom Tromey
2008-10-21 16:27 ` Pedro Alves
2008-10-21 18:56 ` Tom Tromey [this message]
2008-10-21 21:18 ` Tom Tromey
2008-10-21 21:28 ` Pedro Alves
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=m3iqrl93uk.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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