From: Daniel Jacobowitz <drow@mvista.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] selftest.exp: bump up initial line count
Date: Mon, 23 Jun 2003 03:52:00 -0000 [thread overview]
Message-ID: <20030623034409.GA18557@nevyn.them.org> (raw)
In-Reply-To: <200306230301.h5N31cv0012495@duracef.shout.net>
On Sun, Jun 22, 2003 at 11:01:38PM -0400, Michael Elizabeth Chastain wrote:
> This patch fixes one FAIL in gdb.base/selftest.exp.
>
> The procedure 'do_steps_and_nexts' walks through the first few lines of
> 'captured_main' until it reaches the initialization of 'dirarg', or
> walks through 26 lines, whichever comes first. Unfortunately 26 lines
> is no longer enough! This patch simply bumps the limit up to 32.
>
> I tested this on native i686-pc-linux-gnu, red-hat-8.0,
> with gcc v2 and v3, -gdwarf-2 and -gstabs+.
>
> Okay to apply?
Hmm, I am not sure - that doesn't fix the failure here :( Because the
beginning of the xmalloc call (pushing 4 onto the stack) gets scheduled
earlier than the preceding two lines. So the test fails anyway.
Could you try this more comprehensive patch?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
2003-06-22 Michael Chastain <mec@shout.net>
Daniel Jacobowitz <drow@mvista.com>
* gdb.base/selftest.exp (do_steps_and_nexts): Increase maximum
initial line count of 'captured_main' from 26 to 32.
(test_with_self): Allow xmalloc call to be interleaved with the
preceding two lines.
Index: gdb.base/selftest.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/selftest.exp,v
retrieving revision 1.8
diff -u -p -r1.8 selftest.exp
--- gdb.base/selftest.exp 2 Jun 2003 16:02:59 -0000 1.8
+++ gdb.base/selftest.exp 23 Jun 2003 03:42:03 -0000
@@ -1,4 +1,4 @@
-# Copyright 1988, 1990, 1991, 1992, 1994, 1997, 1999, 2000, 2002
+# Copyright 1988, 1990, 1991, 1992, 1994, 1997, 1999, 2000, 2002, 2003
# Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
@@ -52,7 +52,7 @@ proc do_steps_and_nexts {} {
gdb_reinitialize_dir $srcdir/..
- for {set count 0} {$count < 26} {incr count} {
+ for {set count 0} {$count < 32} {incr count} {
send_gdb "list\n"
# NOTE: carlton/2002-12-11: The "initial brace" and
# "current_directory initialization" possibilities happen to
@@ -327,10 +327,31 @@ proc test_with_self { executable } {
# If we don't actually enter the xmalloc call when we give a
# step command that seems like a genuine bug. It seems to happen
# on most RISC processors.
+ # NOTE drow/2003-06-22: However, if we step back to the preceding two
+ # lines, just keep stepping until we enter.
+ set stepped_back 0
setup_xfail "alpha-*-*" "mips-*-*"
set description "step into xmalloc call"
send_gdb "step\n"
gdb_expect {
+ -re "ncmd = 0;.*$gdb_prompt $" {
+ set stepped_back 1
+ send_gdb "step\n"
+ exp_continue
+ }
+ -re "dirsize = 1;.*$gdb_prompt $" {
+ set stepped_back 1
+ send_gdb "step\n"
+ exp_continue
+ }
+ -re ".*dirarg = .* xmalloc.*$gdb_prompt $" {
+ if { $stepped_back == 1 } {
+ send_gdb "step\n"
+ exp_continue
+ } else {
+ fail "$description"
+ }
+ }
-re "xmalloc.*size=.*at.*utils.c.*$gdb_prompt $" {
pass "$description"
}
next prev parent reply other threads:[~2003-06-23 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-23 3:06 Michael Elizabeth Chastain
2003-06-23 3:52 ` Daniel Jacobowitz [this message]
2003-06-23 4:04 Michael Elizabeth Chastain
2003-06-28 16:37 ` Daniel Jacobowitz
2003-06-29 16:33 Michael Elizabeth Chastain
2003-06-29 17:37 ` Daniel Jacobowitz
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=20030623034409.GA18557@nevyn.them.org \
--to=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