From: David Carlton <carlton@kealia.com>
To: gdb <gdb@sources.redhat.com>
Cc: Jeff Johnston <jjohnstn@redhat.com>
Subject: gdb.base/pending.exp failures
Date: Thu, 05 Feb 2004 00:06:00 -0000 [thread overview]
Message-ID: <yf2u126iecu.fsf@hawaii.kealia.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
I'm getting testsuite failures from gdb.base/pending.exp. This is
i686-pc-linux-gnu (Red Hat 8.0, if that matters), lots of different
GCC's.
Usually, I get this:
FAIL: gdb.base/pending.exp: set pending breakpoint
FAIL: gdb.base/pending.exp: single pending breakpoint info
FAIL: gdb.base/pending.exp: pending plus real breakpoint info
FAIL: gdb.base/pending.exp: pending plus condition
FAIL: gdb.base/pending.exp: pending disabled
FAIL: gdb.base/pending.exp: pending disabled plus commands
FAIL: gdb.base/pending.exp: multiple pending breakpoints
FAIL: gdb.base/pending.exp: re-enabling pending breakpoint that can resolve instantly
but sometimes I get this:
FAIL: gdb.base/pending.exp: set pending breakpoint
FAIL: gdb.base/pending.exp: single pending breakpoint info
FAIL: gdb.base/pending.exp: pending plus real breakpoint info
FAIL: gdb.base/pending.exp: pending plus condition
FAIL: gdb.base/pending.exp: pending disabled
FAIL: gdb.base/pending.exp: pending disabled plus commands
FAIL: gdb.base/pending.exp: Set pending breakpoint 2
ERROR: Got interactive prompt.
ERROR: Got interactive prompt.
FAIL: gdb.base/pending.exp: re-enabling pending breakpoint that can resolve instantly
FAIL: gdb.base/pending.exp: continue to resolved breakpoint 2
FAIL: gdb.base/pending.exp: continue to resolved breakpoint 1
Log attached.
David Carlton
carlton@kealia.com
[-- Attachment #2: gdb.log --]
[-- Type: text/plain, Size: 7787 bytes --]
Test Run By carlton on Wed Feb 4 15:59:24 2004
Native configuration is i686-pc-linux-gnu
=== gdb tests ===
Schedule of variations:
unix
Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./gdb.base/pending.exp ...
get_compiler_info: gcc-3-2
Executing on host: gcc -c -g -o /gdb/mirror/src/gdb/testsuite/gdb.base/pending.o ./gdb.base/pending.c (timeout = 300)
spawn gcc -c -g -o /gdb/mirror/src/gdb/testsuite/gdb.base/pending.o ./gdb.base/pending.c
Executing on host: gcc -fpic -c -g -o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.o ./gdb.base/pendshr.c (timeout = 300)
spawn gcc -fpic -c -g -o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.o ./gdb.base/pendshr.c
Executing on host: gcc /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.o -shared -g -lm -o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.sl (timeout = 300)
spawn gcc /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.o -shared -g -lm -o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.sl
Executing on host: gcc /gdb/mirror/src/gdb/testsuite/gdb.base/pending.o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.sl -g -lm -o /gdb/mirror/src/gdb/testsuite/gdb.base/pending (timeout = 300)
spawn gcc /gdb/mirror/src/gdb/testsuite/gdb.base/pending.o /gdb/mirror/src/gdb/testsuite/gdb.base/pendshr.sl -g -lm -o /gdb/mirror/src/gdb/testsuite/gdb.base/pending
spawn /gdb/mirror/src/gdb/testsuite/../../gdb/gdb -nw -nx
GNU gdb 2004-02-04-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
(gdb) set height 0
(gdb) set width 0
(gdb) dir
Reinitialize source path to empty? (y or n) y
Source directories searched: $cdir:$cwd
(gdb) dir ./gdb.base
Source directories searched: /gdb/mirror/src/gdb/testsuite/./gdb.base:$cdir:$cwd
(gdb) file /gdb/mirror/src/gdb/testsuite/gdb.base/pending
Reading symbols from /gdb/mirror/src/gdb/testsuite/gdb.base/pending...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) break pendfunc1
Breakpoint 1 at 0x804839c
(gdb) FAIL: gdb.base/pending.exp: set pending breakpoint
info break
Num Type Disp Enb Address What
1 breakpoint keep y 0x0804839c
(gdb) FAIL: gdb.base/pending.exp: single pending breakpoint info
list pending.c:1,1
1 /* This testcase is part of GDB, the GNU debugger.
(gdb) search break main here
30 pendfunc1 (3); /* break main here */
(gdb) break main
Breakpoint 2 at 0x804847c: file gdb.base/pending.c, line 30.
(gdb) PASS: gdb.base/pending.exp: breakpoint function
info break
Num Type Disp Enb Address What
1 breakpoint keep y 0x0804839c
2 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
(gdb) FAIL: gdb.base/pending.exp: pending plus real breakpoint info
break pendfunc2
Function "pendfunc2" not defined.
Make breakpoint pending on future shared library load? (y or n) n
(gdb) PASS: gdb.base/pending.exp: Don't set pending breakpoint
condition 1 k == 1
(gdb) PASS: gdb.base/pending.exp: condition 1 k == 1
(gdb) info break
Num Type Disp Enb Address What
1 breakpoint keep y 0x0804839c
stop only if k == 1
2 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
(gdb) FAIL: gdb.base/pending.exp: pending plus condition
disable 1
(gdb)
(gdb) PASS: gdb.base/pending.exp: disable 1
info break
Num Type Disp Enb Address What
1 breakpoint keep n 0x0804839c
stop only if k == 1
2 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
(gdb) FAIL: gdb.base/pending.exp: pending disabled
commands 1
Type commands for when breakpoint 1 is hit, one per line.
End with a line saying just "end".
print k
end
>print k
>end
(gdb) PASS: gdb.base/pending.exp: Set commands for pending breakpoint
info break
Num Type Disp Enb Address What
1 breakpoint keep n 0x0804839c
stop only if k == 1
print k
2 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
(gdb) FAIL: gdb.base/pending.exp: pending disabled plus commands
break pendshr.c:26 if x > 3
No source file named pendshr.c.
Make breakpoint pending on future shared library load? (y or n) y
Breakpoint 3 (pendshr.c:26 if x > 3) pending.
(gdb) PASS: gdb.base/pending.exp: Set pending breakpoint 2
info break
Num Type Disp Enb Address What
1 breakpoint keep n 0x0804839c
stop only if k == 1
print k
2 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
3 breakpoint keep y <PENDING> pendshr.c:26 if x > 3
(gdb) FAIL: gdb.base/pending.exp: multiple pending breakpoints
run
Starting program: /gdb/mirror/src/gdb/testsuite/gdb.base/pending
Breakpoint 1 at 0x4001470f: file gdb.base/pendshr.c, line 26.
Note: breakpoint 1 (disabled) also set at pc 0x4001470f.
Breakpoint 4 at 0x4001470f: file gdb.base/pendshr.c, line 26.
Pending breakpoint "pendshr.c:26 if x > 3" resolved
Breakpoint 2, main () at gdb.base/pending.c:30
30 pendfunc1 (3); /* break main here */
(gdb) PASS: gdb.base/pending.exp: running to main
enable 1
(gdb) FAIL: gdb.base/pending.exp: re-enabling pending breakpoint that can resolve instantly
continue
Continuing.
in pendfunc1, x is 3
Breakpoint 4, pendfunc1 (x=4) at gdb.base/pendshr.c:26
26 int y = x + 4;
(gdb) PASS: gdb.base/pending.exp: continue to resolved breakpoint 2
continue
Continuing.
in pendfunc1, x is 4
Breakpoint 1, pendfunc1 (x=3) at gdb.base/pendshr.c:26
26 int y = x + 4;
$1 = 1
(gdb) PASS: gdb.base/pending.exp: continue to resolved breakpoint 1
delete breakpoints
Delete all breakpoints? (y or n) y
(gdb) info breakpoints
No breakpoints or watchpoints.
(gdb) break main
Breakpoint 5 at 0x804847c: file gdb.base/pending.c, line 30.
(gdb) break imaginary
Function "imaginary" not defined.
Make breakpoint pending on future shared library load? (y or n) y
Breakpoint 6 (imaginary) pending.
(gdb) PASS: gdb.base/pending.exp: set imaginary pending breakpoint
run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /gdb/mirror/src/gdb/testsuite/gdb.base/pending
Breakpoint 5, main () at gdb.base/pending.c:30
30 pendfunc1 (3); /* break main here */
(gdb) PASS: gdb.base/pending.exp: rerun to main
info break
Num Type Disp Enb Address What
5 breakpoint keep y 0x0804847c in main at gdb.base/pending.c:30
breakpoint already hit 1 time
6 breakpoint keep y <PENDING> imaginary
(gdb) PASS: gdb.base/pending.exp: verify pending breakpoint after restart
testcase ./gdb.base/pending.exp completed in 1 seconds
=== gdb Summary ===
# of expected passes 12
# of unexpected failures 8
Executing on host: /gdb/mirror/src/gdb/testsuite/../../gdb/gdb -nw --command gdb_cmd (timeout = 300)
spawn /gdb/mirror/src/gdb/testsuite/../../gdb/gdb -nw --command gdb_cmd
GNU gdb 2004-02-04-cvs
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu".
/gdb/mirror/src/gdb/testsuite/../../gdb/gdb version 2004-02-04-cvs -nx
runtest completed at Wed Feb 4 15:59:25 2004
next reply other threads:[~2004-02-05 0:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 0:06 David Carlton [this message]
2004-02-05 0:21 ` Daniel Jacobowitz
2004-02-05 1:03 ` Jeff Johnston
2004-02-05 1:22 ` [PATCH]: " Jeff Johnston
2004-02-05 1:48 ` David Carlton
2004-02-05 4:25 ` 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=yf2u126iecu.fsf@hawaii.kealia.com \
--to=carlton@kealia.com \
--cc=gdb@sources.redhat.com \
--cc=jjohnstn@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