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/29431] New: [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed Date: Fri, 29 Jul 2022 09:15:52 +0000 [thread overview] Message-ID: <bug-29431-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29431 Bug ID: 29431 Summary: [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed 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 testrun on openSUSE Leap 15.3 x86_64 with taskset -c 0, and ran into: ... (gdb) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: print seconds_left detach^M [Thread 0x7f10c6073100 (LWP 5396) exited]^M /home/vries/gdb_versions/devel/src/gdb/thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed.^M A problem internal to GDB has been detected,^M further debugging may prove unreliable.^M ... This is a bit after: ... (gdb) PASS: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break at break_fn: 2 continue^M Continuing.^M Couldn't get registers: No such process.^M (gdb) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: break at break_fn: 3 ... and: ... print again = 1^M Cannot access memory at address 0x6020cc^M (gdb) FAIL: gdb.threads/attach-many-short-lived-threads.exp: iter 1: reset timer in the infer\ ior print seconds_left^M Cannot access memory at address 0x6020ac^M ... -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-07-29 9:15 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-29 9:15 vries at gcc dot gnu.org [this message] 2022-07-29 9:19 ` [Bug gdb/29431] " 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-29431-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).