From: Jason Merrill <jason@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: Jason Merrill <jason@redhat.com>
Subject: PATCH to dejagnu/lib/remote.exp:check_for_board_status
Date: Thu, 28 Feb 2002 03:09:00 -0000 [thread overview]
Message-ID: <wvly9hdq2xi.fsf@prospero.cambridge.redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
The status wrapper adds "<EOL>*** EXIT code n<EOL>" to the output.
check_for_board_status tries to strip this, but the old regexp would only
strip a CR or an LF, not both, so we were left with a trailing CR if the
target uses the DOS EOL convention. Fixed thus.
OK?
2002-02-28 Jason Merrill <jason@redhat.com>
* lib/remote.exp (check_for_board_status): Remove both CR and LF
at the beginning of the status wrapper output.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: text/x-patch, Size: 928 bytes --]
*** remote.exp.~1~ Thu Feb 28 10:44:49 2002
--- remote.exp Thu Feb 28 02:31:07 2002
*************** proc check_for_board_status { variable
*** 1057,1063 ****
if [regexp "(^|\[\r\n\])\\*\\*\\* EXIT code" $output] {
regsub "^.*\\*\\*\\* EXIT code " $output "" result;
regsub "\[\r\n\].*$" $result "" result;
! regsub -all "(^|\[\r\n\])\\*\\*\\* EXIT code \[^\r\n\]*(\[\r\n\]\[\r\n\]?|$)" $output "" output;
regsub "^\[^0-9\]*" $result "" result
regsub "\[^0-9\]*$" $result "" result
verbose "got board status $result" 3
--- 1057,1063 ----
if [regexp "(^|\[\r\n\])\\*\\*\\* EXIT code" $output] {
regsub "^.*\\*\\*\\* EXIT code " $output "" result;
regsub "\[\r\n\].*$" $result "" result;
! regsub -all "(^|\r?\n)\\*\\*\\* EXIT code \[^\r\n\]*(\r?\n|$)" $output "" output;
regsub "^\[^0-9\]*" $result "" result
regsub "\[^0-9\]*$" $result "" result
verbose "got board status $result" 3
next reply other threads:[~2002-02-28 11:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 3:09 Jason Merrill [this message]
2002-04-14 14:06 ` Jason Merrill
2002-04-14 14:24 ` Andrew Cagney
2002-04-14 14:31 ` Jason Merrill
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=wvly9hdq2xi.fsf@prospero.cambridge.redhat.com \
--to=jason@redhat.com \
--cc=gdb-patches@sources.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