From: Thomas Schwinge <thomas@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org, Kevin Buettner <kevinb@redhat.com>
Subject: Re: Testsuite regression for annota1.exp and annota3.exp [Re: [PATCH] [SH] ... can do this signal stuff!]
Date: Tue, 28 Feb 2012 23:27:00 -0000 [thread overview]
Message-ID: <87y5rm4lvo.fsf@schwinge.name> (raw)
In-Reply-To: <20120228194137.GA947@host2.jankratochvil.net>
[-- Attachment #1: Type: text/plain, Size: 1041 bytes --]
Hi!
On Tue, 28 Feb 2012 20:41:37 +0100, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> On Tue, 28 Feb 2012 20:08:30 +0100, Thomas Schwinge wrote:
> > 142db50201b1b1c69ebdc2dcdb1181cde1db3b08 I got the idea of using [concat
> > ...] for building gdb_expect_list's third list argument -- it needs to
> > expand $main_line, etc. Any better suggestions (I obviously don't have a
> > lot of TCL and/or GDB testcase writing experience), or is this
> > acceptable?
>
> I find it OK.
Thanks for reviewing this quickly.
> Please edit in your patch:
> > + "Breakpoint.*at.* file .*$srcfile, line $main_line\." \
> ->
> + "Breakpoint.*at.* file .*$srcfile, line $main_line\\." \
>
> (as \. is just TCL character . and regex then just gets ., not \.)
Makes sense; re-tested and then committed with that change. There are,
of course, other similar inaccuracies, such as an unquoted dot after
expanding $srcfile in the line that you quoted above, but that's a
separate cleanup project.
Grüße,
Thomas
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2012-02-28 22:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 10:03 [PATCH] [SH] ... can do this signal stuff! Thomas Schwinge
2012-02-28 13:43 ` Pedro Alves
2012-02-28 16:05 ` Testsuite regression for annota1.exp and annota3.exp [Re: [PATCH] [SH] ... can do this signal stuff!] Jan Kratochvil
2012-02-28 19:42 ` Thomas Schwinge
2012-02-28 19:43 ` Jan Kratochvil
2012-02-28 23:27 ` Thomas Schwinge [this message]
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=87y5rm4lvo.fsf@schwinge.name \
--to=thomas@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=kevinb@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