From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: [patch] Remove comments from user_code in gdb_test_multiple
Date: Thu, 27 Mar 2008 15:24:00 -0000 [thread overview]
Message-ID: <47EBBBFA.4010700@de.ibm.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 424 bytes --]
Hi,
this patch removes all comments from user_code given to gdb_test_multiple. This allows
to have comments in code snippets given to gdb_test_multiple like for exmaple proposed
in this patch:
http://sourceware.org/ml/gdb-patches/2008-03/msg00290.html
ChangeLog:
* lib/gdb.exp (gdb_test_multiple): Remove comments from user_code.
Ok ?
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
[-- Attachment #2: gdb_multiple_cmt --]
[-- Type: text/plain, Size: 532 bytes --]
diff -urpN src/gdb/testsuite/lib/gdb.exp dev/gdb/testsuite/lib/gdb.exp
--- src/gdb/testsuite/lib/gdb.exp 2008-03-10 11:23:52.000000000 +0100
+++ dev/gdb/testsuite/lib/gdb.exp 2008-03-27 16:15:08.000000000 +0100
@@ -566,6 +566,7 @@ proc gdb_test_multiple { command message
# input doesn't contain a pattern which contains actual embedded newlines
# at this point!
+ regsub -all {[;#].*?[\n]} ${user_code} { } user_code
regsub -all {\n} ${user_code} { } subst_code
set subst_code [uplevel list $subst_code]
next reply other threads:[~2008-03-27 15:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 15:24 Markus Deuling [this message]
2008-03-27 15:32 ` Daniel Jacobowitz
2008-03-27 15:47 ` Markus Deuling
2008-03-27 15:55 ` Daniel Jacobowitz
2008-03-27 17:52 ` Ulrich Weigand
2008-03-28 9:16 ` Markus Deuling
2008-03-28 16:00 ` Ulrich Weigand
2008-03-31 8:42 ` Markus Deuling
2008-03-27 16:35 ` Andrew STUBBS
2008-03-28 8:57 ` Markus Deuling
2008-03-28 9:40 ` Andrew STUBBS
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=47EBBBFA.4010700@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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