Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 4/4] Test on solib load and unload
Date: Mon, 04 Nov 2013 17:37:00 -0000	[thread overview]
Message-ID: <87ob60uo9j.fsf@fleche.redhat.com> (raw)
In-Reply-To: <52746817.7060902@codesourcery.com> (Yao Qi's message of "Sat, 2	Nov 2013 10:48:55 +0800")

>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> Using a list makes caller code cleaner if multiple lines are written.
Yao> I am fine to use one big string here.

You can always join a list in the caller:

   set list [however-you-make-it]
   gdb_produce_source filename [join $list \n]

Yao> 	* lib/gdb.exp (gdb_produce_source): New procedure.
Yao> 	* gdb.perf/solib.c: New.
Yao> 	* gdb.perf/solib.exp: New.
Yao> 	* gdb.perf/solib.py: New.

Looks good to me, thanks.

Tom


  reply	other threads:[~2013-11-04 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  7:36 [PATCH 0/4 V4] GDB Performance testing Yao Qi
2013-11-01  7:36 ` [PATCH 2/4] Perf test framework Yao Qi
2013-11-01 19:43   ` Doug Evans
2013-11-01 20:46   ` Tom Tromey
2013-11-02  2:42     ` Yao Qi
2013-11-04 16:27       ` Tom Tromey
2013-11-06  5:30         ` Yao Qi
2013-11-01  7:36 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-11-01 20:35   ` Tom Tromey
2013-11-02  2:50     ` Yao Qi
2013-11-04 17:37       ` Tom Tromey [this message]
2013-11-01  7:36 ` [PATCH 3/4] Mention perf test in testsuite/README Yao Qi
2013-11-01  7:36 ` [PATCH 1/4] New make target 'check-perf' and new dir gdb.perf Yao Qi
2013-11-06  6:42 ` [PATCH 0/4 V4] GDB Performance testing Yao Qi
  -- strict thread matches above, loose matches on Subject: below --
2013-10-16  7:10 [PATCH 0/4 V3] " Yao Qi
2013-10-16  7:10 ` [PATCH 4/4] Test on solib load and unload Yao Qi
2013-10-25  7:17   ` Doug Evans

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=87ob60uo9j.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@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