Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org,  tromey@redhat.com
Subject: Re: RFA: fix PR 2506
Date: Tue, 21 Oct 2008 16:27:00 -0000	[thread overview]
Message-ID: <200810211727.18574.pedro@codesourcery.com> (raw)
In-Reply-To: <m3zln7ku62.fsf@fleche.redhat.com>

Hi Tom,

Thanks for working on this.

On Thursday 21 August 2008 02:56:21, Tom Tromey wrote:

> PR 2506 is about string concatenation.

> 2008-08-20  Tom Tromey  <tromey@redhat.com>
> 
> 	PR gdb/2506:
> 	* c-exp.y (string_exp): New production.
> 	(exp): Use it.
> 
> 2008-08-20  Tom Tromey  <tromey@redhat.com>
> 
> 	* gdb.base/exprs.exp (test_expr): Add test for string
> 	concatenation.
> 

This crashes for me:

 print "foo" "bar" "boo"

:-(

Also, these files don't use xmalloc/xfree.  Instead, one writes
malloc/free; they're sed'ed by the build system --- see the top of
c-exp.y.

-- 
Pedro Alves


  reply	other threads:[~2008-10-21 16:27 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 [this message]
2008-10-21 18:56   ` Tom Tromey
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=200810211727.18574.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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