From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix racy test in gdb.threads/thread-specific-bp.exp
Date: Tue, 04 Apr 2017 08:08:00 -0000 [thread overview]
Message-ID: <86r318zjbq.fsf@gmail.com> (raw)
In-Reply-To: <27d2906cc62411453861a5868a38bff8@polymtl.ca> (Simon Marchi's message of "Mon, 03 Apr 2017 21:49:01 -0400")
Simon Marchi <simon.marchi@polymtl.ca> writes:
> I am not sure I understand what this is supposed to match. First are
> the parenthesis useful, since we're not using any capture group?
I don't capture anything.
> Then, .* followed with [^\r\n]* doesn't seem useful, since the .* can
> just match anything the [^\r\n]* doesn't match.
>
> What about just this?
>
> set test "continue to end"
> gdb_test_multiple "$cmd" $test {
> -re "hit Breakpoint $decimal, end \\(\\) at.*$gdb_prompt " {
We should still keep \r\n before $gdb_prompt.
> pass $test
> }
> }
The original pattern is "end .* at", so I want to leave it there, and
change it to
set test "continue to end"
gdb_test_multiple "$cmd" $test {
-re "Breakpoint .* end .* at .*\r\n$gdb_prompt " {
pass $test
}
}
--
Yao (齐尧)
next prev parent reply other threads:[~2017-04-04 8:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 21:06 Yao Qi
2017-04-04 1:49 ` Simon Marchi
2017-04-04 8:08 ` Yao Qi [this message]
2017-04-04 13:37 ` Simon Marchi
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=86r318zjbq.fsf@gmail.com \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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