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] [gdb] thread.c:805: internal-error: thread_change_ptid: Assertion `tp != nullptr' failed
Date: Fri, 29 Jul 2022 09:19:01 +0000	[thread overview]
Message-ID: <bug-29431-4717-y5K965yxdO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29431-4717@http.sourceware.org/bugzilla/>

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.

      reply	other threads:[~2022-07-29  9:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29  9:15 [Bug gdb/29431] New: " vries at gcc dot gnu.org
2022-07-29  9:19 ` vries at gcc dot gnu.org [this message]

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