public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/27908] New: FAIL: gdb.base/run-attach-while-running.exp: threaded=1: run-or-attach=attach: non-stop=on: test: attach to process (timeout)
Date: Tue, 25 May 2021 08:44:09 +0000 [thread overview]
Message-ID: <bug-27908-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27908
Bug ID: 27908
Summary: FAIL: gdb.base/run-attach-while-running.exp:
threaded=1: run-or-attach=attach: non-stop=on: test:
attach to process (timeout)
Product: gdb
Version: 10.1
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
I build gdb with -O2 -g (instead of the usual -O0 -g) and ran the testsuite.
With test-case gdb.base/run-attach-while-running.exp, I ran into:
...
FAIL: gdb.base/run-attach-while-running.exp: threaded=1: run-or-attach=attach:
non-stop=on: test: attach to process (timeout)
...
In more detail:
...
(gdb) PASS: gdb.base/run-attach-while-running.exp: threaded=1:
run-or-attach=attach: non-stop=on: test: set confirm off
spawn
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/run-attach-while-running/run-attach-while-running-threads^M
attach 18201^M
Attaching to program:
/home/vries/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.base/run-attach-while-running/run-attach-while-running-threads,
process 18201^M
[New LWP 18206]^M
Reading symbols from /lib64/libpthread.so.0...^M
Reading symbols from
/usr/lib/debug/lib64/libpthread-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
[Thread debugging using libthread_db enabled]^M
Using host libthread_db library "/lib64/libthread_db.so.1".^M
Reading symbols from /lib64/libm.so.6...^M
Reading symbols from
/usr/lib/debug/lib64/libm-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
Reading symbols from /lib64/libc.so.6...^M
Reading symbols from
/usr/lib/debug/lib64/libc-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
Reading symbols from /lib64/ld-linux-x86-64.so.2...^M
Reading symbols from
/usr/lib/debug/lib64/ld-2.26.so-2.26-lp152.26.6.1.x86_64.debug...^M
0x00007f13c85a74c0 in __GI___nanosleep
(requested_time=requested_time@entry=0x7ffc00aa0b60,
remaining=remaining@entry=0x7ffc00aa0b60) at
../sysdeps/unix/sysv/linux/nanosleep.c:27^M
27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining);^M
(gdb) ^M
Thread 2 "run-attach-whil" stopped.^M
0x00007f13c85a74c0 in __GI___nanosleep
(requested_time=requested_time@entry=0x7f13c84dcea0,
remaining=remaining@entry=0x7f13c84dcea0) at
../sysdeps/unix/sysv/linux/nanosleep.c:27^M
27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining);^M
FAIL: gdb.base/run-attach-while-running.exp: threaded=1: run-or-attach=attach:
non-stop=on: test: attach to process (timeout)
killing 18201
Executing on build: kill -9 18201 (timeout = 300)
spawn -ignore SIGHUP kill -9 18201^M
closing exp24
waiting for exp24
testcase
/home/vries/gdb_versions/devel/src/gdb/testsuite/gdb.base/run-attach-while-running.exp
completed in 23 seconds
...
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-05-25 8:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:44 vries at gcc dot gnu.org [this message]
2021-05-25 8:46 ` [Bug gdb/27908] " vries at gcc dot gnu.org
2021-05-25 8:47 ` vries at gcc dot gnu.org
2021-05-25 9:13 ` vries at gcc dot gnu.org
2021-05-25 9:25 ` vries at gcc dot gnu.org
2021-05-25 9:25 ` vries at gcc dot gnu.org
2021-05-25 10:00 ` vries at gcc dot gnu.org
2021-05-25 10:06 ` vries at gcc dot gnu.org
2021-05-25 10:18 ` vries at gcc dot gnu.org
2021-05-25 11:37 ` vries at gcc dot gnu.org
2021-05-25 12:35 ` vries at gcc dot gnu.org
2021-06-07 13:29 ` [Bug testsuite/27908] " vries at gcc dot gnu.org
2021-06-07 13:46 ` cvs-commit at gcc dot gnu.org
2021-06-07 13:47 ` vries at gcc dot gnu.org
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=bug-27908-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).