public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/29830] New: FAIL: gdb.server/stop-reply-no-thread-multi.exp: target-non-stop=off: to_disable=: stepi
Date: Mon, 28 Nov 2022 02:51:28 +0000 [thread overview]
Message-ID: <bug-29830-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29830
Bug ID: 29830
Summary: FAIL: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: stepi
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: simark at simark dot ca
Target Milestone: ---
I have seen this once on my CI:
308094 (gdb) continue^M
1308095 Continuing.^M
1308096 warning: Could not load shared library symbols for linux-vdso.so.1.^M
1308097 Do you need "set solib-search-path" or "set sysroot"?^M
1308098 [New Thread 1459184]^M
1308099 ^M
1308100 Thread 1 hit Breakpoint 1, unlock_worker () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-extended-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.server/stop-reply-no-thre
ad-multi.c:28^M
1308101 28 worker_blocked = 0;^M
1308102 (gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: continue to breakpoint: run to unlock_worker
1308103 info threads^M
1308104 Id Target Id Frame ^M
1308105 * 1 Thread 1459169 unlock_worker () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-extended-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.server/stop-reply-no-thread
-multi.c:28^M
1308106 2 Thread 1459184 unlock_main () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-extended-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.server/stop-reply-no-thread-m
ulti.c:35^M
1308107 (gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: second thread should now exist
1308108 thread 2^M
1308109 [Switching to thread 2 (Thread 1459184)]^M
1308110 #0 unlock_main () at
/home/jenkins/workspace/binutils-gdb_master_linuxbuild/platform/jammy-amd64/target_board/native-extended-gdbserver/src/binutils-gdb/gdb/testsuite/gdb.server/stop-reply-no-thread-multi.c:35^M
1308111 35 }^M
1308112 (gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: switch to second thread
1308113 set scheduler-locking on^M
1308114 (gdb) PASS: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: set scheduler-locking on
1308115 stepi^M
1308116 0x00005555555551d1 35 }^M
1308117 (gdb) FAIL: gdb.server/stop-reply-no-thread-multi.exp:
target-non-stop=off: to_disable=: stepi
I haven't been able to reproduce it locally.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-11-28 2:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 2:51 simark at simark dot ca [this message]
2022-11-28 2:51 ` [Bug gdb/29830] With native-extended-gdbserver board, " simark at simark dot ca
2022-11-28 2:52 ` simark at simark dot ca
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-29830-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).