From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] testsuite: bigcore.exp fuzzy PASS message fix
Date: Sun, 29 Nov 2009 15:12:00 -0000 [thread overview]
Message-ID: <20091129151207.GA27126@host0.dyn.jankratochvil.net> (raw)
Hi,
seen needlessly fuzzy results:
-PASS: gdb.base/bigcore.exp: extract next heap (stop at 50)
-PASS: gdb.base/bigcore.exp: extract prev heap (stop at 50)
+PASS: gdb.base/bigcore.exp: extract next heap
+PASS: gdb.base/bigcore.exp: extract prev heap
but the .exp file just is not patient enough:
-Total of 4292375328 (0xffd87320) bytes bytes 53 chunks
+Total of 4292422432 (0xffd92b20) bytes bytes 41 chunks
Increased to 200. Tested on {x86_64,x86_64-m32}-fedora12-linux-gnu.
Thanks,
Jan
gdb/testsuite/
2009-11-29 Jan Kratochvil <jan.kratochvil@redhat.com>
* gdb.base/bigcore.exp (extract_heap): Set $lim limit to 200.
--- a/gdb/testsuite/gdb.base/bigcore.exp
+++ b/gdb/testsuite/gdb.base/bigcore.exp
@@ -96,7 +96,7 @@ proc extract_heap { dir } {
}
-re " = \\(struct list \\*\\) (0x\[0-9a-f\]*).*$gdb_prompt $" {
set heap [concat $heap $expect_out(1,string)]
- if { $lim >= 50 } {
+ if { $lim >= 200 } {
pass "$test (stop at $lim)"
} else {
incr lim
next reply other threads:[~2009-11-29 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 15:12 Jan Kratochvil [this message]
2009-11-30 20:25 ` Tom Tromey
2009-11-30 22:58 ` Jan Kratochvil
2009-12-21 5:49 ` Joel Brobecker
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=20091129151207.GA27126@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.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