From: Stephane Carrez <stcarrez@nerim.fr>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Fix testsuite/gdb.base/break.exp when test compiled with -DPROTOTYPES
Date: Sat, 05 Apr 2003 10:46:00 -0000 [thread overview]
Message-ID: <3E8EB3F4.8040109@nerim.fr> (raw)
In-Reply-To: <20030404222839.GA18941@nevyn.them.org>
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Hi!
Daniel Jacobowitz wrote:
> On Fri, Apr 04, 2003 at 11:31:37PM +0200, Stephane Carrez wrote:
>
>>Hi!
>>
>>Michael Elizabeth Chastain wrote:
>>
>>>I could be wrong, but I don't think you can put comments in the
>>>middle of a gdb_expect block like this.
>>>
>>> + # marker4() is defined at line 46 when compiled with -DPROTOTYPES
>>> + -re "Breakpoint $decimal, marker4 \\(d=177601976\\) at
>>> .*$srcfile:46\[\r\n\]+46\[\t \]+void marker4.*" {
>>> + pass "run until breakpoint set at small function, optimized file"
>>> + }
>>>
>>>I think you have to do this:
>>>
>>> -re "Breakpoint ... void marker.*" {
>>> # marker4() is defined at line 46 when compiled with -DPROTOTYPES
>>> pass "run until breakpoint set at small function, optimized file"
>>> }
>>>
>>>Michael C
>>>
>>>
>>
>>I wasn't sure too..
>>
>>But I verified that it worked before the commit...
>
>
> It may have worked, but Michael is right. It will parse the comment as
> a series of patterns and code blocks.
>
Ok, it's very bad then. I've removed the patch.
Stephane
2003-04-05 Stephane Carrez <stcarrez@nerim.fr>
* gdb.base/break.exp: Revert last patch.
[-- Attachment #2: break.exp.diffs --]
[-- Type: text/plain, Size: 920 bytes --]
Index: gdb.base/break.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.exp,v
retrieving revision 1.15
diff -u -p -r1.15 break.exp
--- gdb.base/break.exp 4 Apr 2003 20:03:46 -0000 1.15
+++ gdb.base/break.exp 5 Apr 2003 10:40:04 -0000
@@ -914,10 +914,6 @@ gdb_expect {
-re "Breakpoint $decimal, $hex in marker4 \\(d=177601976\\) at .*$srcfile:51\[\r\n\]+51\[\t \]+void marker4.*" {
pass "run until breakpoint set at small function, optimized file"
}
- # marker4() is defined at line 46 when compiled with -DPROTOTYPES
- -re "Breakpoint $decimal, marker4 \\(d=177601976\\) at .*$srcfile:46\[\r\n\]+46\[\t \]+void marker4.*" {
- pass "run until breakpoint set at small function, optimized file"
- }
-re ".*$gdb_prompt " {
fail "run until breakpoint set at small function, optimized file"
}
next prev parent reply other threads:[~2003-04-05 10:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 20:41 Michael Elizabeth Chastain
2003-04-04 21:31 ` Stephane Carrez
2003-04-04 22:29 ` Daniel Jacobowitz
2003-04-05 10:46 ` Stephane Carrez [this message]
2003-04-05 13:20 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2003-02-24 21:19 Stephane Carrez
2003-02-24 21:34 ` Elena Zannoni
2003-02-24 21:46 ` Stephane Carrez
2003-02-24 23:34 ` Jason Molenda
2003-04-04 20:09 ` Stephane Carrez
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=3E8EB3F4.8040109@nerim.fr \
--to=stcarrez@nerim.fr \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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