From: Stephane Carrez <stcarrez@nerim.fr>
To: gdb-patches@sources.redhat.com, gdb-prs@sources.redhat.com,
stcarrez@nerim.fr, gdb-gnats@sources.redhat.com
Subject: Re: testsuite/1096: [RFA]: Fix testsuite/gdb.base/break.exp when test compiled with -DPROTOTYPES
Date: Sat, 05 Apr 2003 11:43:00 -0000 [thread overview]
Message-ID: <3E8EC160.4010305@nerim.fr> (raw)
In-Reply-To: <20030405105120.28085.qmail@sources.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
Hi!
This new patch takes into account Daniel and Michael remarks.
(verified by running gdb testsuite on m6811-elf)
Ok to commit?
Stephane
2003-04-05 Stephane Carrez <stcarrez@nerim.fr>
* gdb.base/break.exp: marker4() is defined at line 46 when compiled
with -DPROTOTYPES.
[-- Attachment #2: break.exp.diffs --]
[-- Type: text/plain, Size: 908 bytes --]
Index: gdb.base/break.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.exp,v
retrieving revision 1.16
diff -u -p -r1.16 break.exp
--- gdb.base/break.exp 5 Apr 2003 10:40:59 -0000 1.16
+++ gdb.base/break.exp 5 Apr 2003 10:52:56 -0000
@@ -914,6 +914,10 @@ 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"
}
+ -re "Breakpoint $decimal, marker4 \\(d=177601976\\) at .*$srcfile:46\[\r\n\]+46\[\t \]+void marker4.*" {
+ # marker4() is defined at line 46 when compiled with -DPROTOTYPES
+ pass "run until breakpoint set at small function, optimized file (line 46)"
+ }
-re ".*$gdb_prompt " {
fail "run until breakpoint set at small function, optimized file"
}
next parent reply other threads:[~2003-04-05 11:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030405105120.28085.qmail@sources.redhat.com>
2003-04-05 11:43 ` Stephane Carrez [this message]
2003-04-05 13:21 ` Andrew Cagney
2003-04-05 16:23 Michael Elizabeth Chastain
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=3E8EC160.4010305@nerim.fr \
--to=stcarrez@nerim.fr \
--cc=gdb-gnats@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-prs@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