public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/29431] New: [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed
@ 2022-07-29  9:15 vries at gcc dot gnu.org
  2022-07-29  9:19 ` [Bug gdb/29431] " vries at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-29  9:15 UTC (permalink / raw)
  To: gdb-prs

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug gdb/29431] [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed
  2022-07-29  9:15 [Bug gdb/29431] New: [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed vries at gcc dot gnu.org
@ 2022-07-29  9:19 ` vries at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: vries at gcc dot gnu.org @ 2022-07-29  9:19 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=29431

--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Created attachment 14241
  --> https://sourceware.org/bugzilla/attachment.cgi?id=14241&action=edit
gdb.log

Note btw that the assertion triggers more often:
...
$ grep -c Assert gdb.log
27
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2022-07-29  9:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-29  9:15 [Bug gdb/29431] New: [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed vries at gcc dot gnu.org
2022-07-29  9:19 ` [Bug gdb/29431] " vries at gcc dot gnu.org

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).