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/25674] New: Error while reading shared library symbols for /lib64/libpthread.so.0: Cannot find user-level thread for LWP : generic error Date: Sat, 14 Mar 2020 13:24:39 +0000 [thread overview] Message-ID: <bug-25674-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=25674 Bug ID: 25674 Summary: Error while reading shared library symbols for /lib64/libpthread.so.0: Cannot find user-level thread for LWP : generic error Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: vries at gcc dot gnu.org Target Milestone: --- I did a gdb test run with check-read1, and ran into: ... FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: no new threads (timeout) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: set breakpoint always-inserted on FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break break_fn FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: reset timer in the inferior FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: detach FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: set breakpoint always-inserted off FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: info breakpoints (got interactive prompt) ERROR: breakpoints not deleted ... But when trying to reproduce this by just running that test-case (in parallel with "stress -c 5", on a dual-core 4 thread cpu), I didn't manage to reproduce at exactly that point, only later in the test-case. However, when looking at the first bit in the gdb.log, I found: ... (gdb) attach 8734^M Attaching to program: /data/gdb_versions/devel/build/gdb/testsuite/outputs/gdb.threads/attach-many-short-lived-threads/attach-many-short-lived-threads, process 8734^M [New LWP 1776]^M [New LWP 1781]^M [New LWP 1783]^M ... [New LWP 2047]^M [New LWP 2048]^M [New LWP 2049]^M [New LWP 2050]^M Error while reading shared library symbols for /lib64/libpthread.so.0:^M Cannot find user-level thread for LWP 1810: generic error^M [LWP 1789 exited]^M [LWP 1810 exited]^M [LWP 1776 exited]^M [LWP 1783 exited]^M [LWP 1788 exited]^M [LWP 1781 exited]^M 0x00007f452a3030f0 in __GI___nanosleep (requested_time=requested_time@entry=0x7ffdb200ab90, remaining=remaining@entry=0x7ffdb200ab90) at ../sysdeps/unix/sysv/linux/nanosleep.c:27^M 27 return SYSCALL_CANCEL (nanosleep, requested_time, remaining);^M (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 1: attach ... We can see that thread 1810 has exited, so the "Cannot find user-level thread for LWP 1810: generic error" part of the message looks correct. It's not clear however, why we should be accessing this user thread while trying to read symbols. Anyway, the thread error message is from an exception which seems to have interrupted symbols reading, and I think that is a bug. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-03-14 13:24 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-14 13:24 vries at gcc dot gnu.org [this message] 2021-03-04 7:16 ` [Bug gdb/25674] " a3at.mail at gmail dot com
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-25674-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: linkBe 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).