From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 3/4] Transform \r\n in MI variables
Date: Tue, 17 Sep 2013 13:07:00 -0000 [thread overview]
Message-ID: <1379423179-8515-4-git-send-email-yao@codesourcery.com> (raw)
In-Reply-To: <1379423179-8515-1-git-send-email-yao@codesourcery.com>
The previous patch can't transform \r\n in variables, so this patch
update these variables which have \r\n in MI.
gdb/testsuite:
2013-09-17 Yao Qi <yao@codesourcery.com>
* lib/mi-support.exp (mi_gdb_prompt): Replace "\r\n" with
"\r+\n".
(thread_selected_re): Likewise.
(gdbindex_warning_re): Likewise.
(library_loaded_re): Likewise.
(breakpoint_re): Likewise.
---
gdb/testsuite/lib/mi-support.exp | 10 +++++-----
1 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/gdb/testsuite/lib/mi-support.exp b/gdb/testsuite/lib/mi-support.exp
index a9b22c2..86f91ac 100644
--- a/gdb/testsuite/lib/mi-support.exp
+++ b/gdb/testsuite/lib/mi-support.exp
@@ -21,7 +21,7 @@
# Set it if it is not already set.
global mi_gdb_prompt
if ![info exists mi_gdb_prompt] then {
- set mi_gdb_prompt "\[(\]gdb\[)\] \r\n"
+ set mi_gdb_prompt "\[(\]gdb\[)\] \r+\n"
}
global mi_inferior_spawn_id
@@ -29,10 +29,10 @@ global mi_inferior_tty_name
set MIFLAGS "-i=mi"
-set thread_selected_re "=thread-selected,id=\"\[0-9\]+\"\r\n"
-set gdbindex_warning_re "&\"warning: Skipping \[^\r\n\]+ \.gdb_index section in \[^\r\n\]+\"\r\n(?:&\"\\\\n\"\r\n)?"
-set library_loaded_re "=library-loaded\[^\n\]+\"\r\n(?:$gdbindex_warning_re)?"
-set breakpoint_re "=(?:breakpoint-created|breakpoint-deleted)\[^\n\]+\"\r\n"
+set thread_selected_re "=thread-selected,id=\"\[0-9\]+\"\r+\n"
+set gdbindex_warning_re "&\"warning: Skipping \[^\r\n\]+ \.gdb_index section in \[^\r\n\]+\"\r+\n(?:&\"\\\\n\"\r+\n)?"
+set library_loaded_re "=library-loaded\[^\n\]+\"\r+\n(?:$gdbindex_warning_re)?"
+set breakpoint_re "=(?:breakpoint-created|breakpoint-deleted)\[^\n\]+\"\r+\n"
#
# mi_gdb_exit -- exit the GDB, killing the target program if necessary
--
1.7.7.6
next prev parent reply other threads:[~2013-09-17 13:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 1:07 [PATCH] native mingw32 gdb, eol format Yao Qi
2013-07-16 2:50 ` Eli Zaretskii
2013-07-20 0:38 ` Yao Qi
2013-07-20 6:55 ` Eli Zaretskii
2013-07-23 19:03 ` Tom Tromey
2013-07-23 19:08 ` Eli Zaretskii
2013-07-23 20:58 ` Tom Tromey
2013-07-24 3:46 ` Eli Zaretskii
2013-07-24 9:09 ` Yao Qi
2013-09-17 13:07 ` [PATCH 0/4] Match \r\r\n in testsuite Yao Qi
2013-09-17 13:07 ` [PATCH 1/4] Use gdb_test_sequence to test "info tracepoints" Yao Qi
2013-09-17 13:07 ` [PATCH 4/4] Replace "." with "\r+" Yao Qi
2013-09-17 13:07 ` [PATCH 2/4] Transform "\r\n" in pattern to "\r+\n" Yao Qi
2013-09-17 23:11 ` Pierre Muller
2013-09-17 13:07 ` Yao Qi [this message]
2013-09-17 13:35 ` [PATCH 0/4] Match \r\r\n in testsuite Joel Brobecker
2013-09-17 13:59 ` Yao Qi
2013-09-17 14:06 ` Joel Brobecker
2013-09-18 8:21 ` Yao Qi
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=1379423179-8515-4-git-send-email-yao@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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