From: Luke Dalessandro <ldalessandro@gmail.com>
To: gdb@sourceware.org
Subject: internal-error inferior_thread(): Assertion `tp' failed
Date: Thu, 20 Apr 2017 14:13:00 -0000 [thread overview]
Message-ID: <F24E67E5-CC2F-45E5-9833-C6476B683B83@gmail.com> (raw)
One of my main uses of gdb is to attach to multithreaded valgrind processes run as `valgrind --vgdb=yes --vgdb-error=0`
With recent builds of gdb I have started to encounter this assertion when the valgrind process is creating new threads.
thread.c:89: internal-error: thread_info* inferior_thread(): Assertion `tp' failed.
I suspect that this has something to do with my environment (I’m configuring and running from a $HOME relative prefix), but the assertion itself doesn’t given me much information to go on, google has been unhelpful, and I’m not aware of any specific changes that I’ve made to my environment.
Does anyone have experience with this problem?
Thanks,
Luke
From gdb-return-45723-listarch-gdb=sources.redhat.com@sourceware.org Thu Apr 20 15:45:47 2017
Return-Path: <gdb-return-45723-listarch-gdb=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb@sources.redhat.com
Received: (qmail 8894 invoked by alias); 20 Apr 2017 15:45:46 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Delivered-To: mailing list gdb@sourceware.org
Received: (qmail 8760 invoked by uid 89); 20 Apr 2017 15:45:41 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_SOFTFAIL autolearn=no version=3.3.2 spammy=HOME, chances
X-HELO: simark.ca
Received: from simark.ca (HELO simark.ca) (158.69.221.121) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 20 Apr 2017 15:45:39 +0000
Received: by simark.ca (Postfix, from userid 33) id 4A9461E48E; Thu, 20 Apr 2017 11:45:39 -0400 (EDT)
To: Luke Dalessandro <ldalessandro@gmail.com>
Subject: Re: internal-error inferior_thread(): Assertion `tp' failed
X-PHP-Originating-Script: 33:rcube.php
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Date: Thu, 20 Apr 2017 15:45:00 -0000
From: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
In-Reply-To: <F24E67E5-CC2F-45E5-9833-C6476B683B83@gmail.com>
References: <F24E67E5-CC2F-45E5-9833-C6476B683B83@gmail.com>
Message-ID: <e62820802979355efb778f100f8f2535@polymtl.ca>
X-Sender: simon.marchi@polymtl.ca
User-Agent: Roundcube Webmail/1.2.4
X-IsSubscribed: yes
X-SW-Source: 2017-04/txt/msg00026.txt.bz2
Content-length: 1229
On 2017-04-20 10:13, Luke Dalessandro wrote:
> One of my main uses of gdb is to attach to multithreaded valgrind
> processes run as `valgrind --vgdb=yes --vgdb-error=0`
>
> With recent builds of gdb I have started to encounter this assertion
> when the valgrind process is creating new threads.
>
> thread.c:89: internal-error: thread_info* inferior_thread():
> Assertion `tp' failed.
>
> I suspect that this has something to do with my environment (Iâm
> configuring and running from a $HOME relative prefix), but the
> assertion itself doesnât given me much information to go on, google
> has been unhelpful, and Iâm not aware of any specific changes that
> Iâve made to my environment.
>
> Does anyone have experience with this problem?
>
> Thanks,
> Luke
Hi Luke,
This error is quite generic. It means that the currently selected
thread in GDB (identified by a process/thread id) doesn't have a
corresponding entry in the GDB thread list. That's definitely a GDB
bug, since it's a state it shouldn't be in.
If you want to increase the chances of someone looking at the problem,
you should provide an easy way to reproduce your problem (small test
program, gdb commands used, etc).
Thanks,
Simon
next reply other threads:[~2017-04-20 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 14:13 Luke Dalessandro [this message]
[not found] ` <e62820802979355efb778f100f8f2535@polymtl.ca>
2017-04-20 16:08 ` Luke Dalessandro
[not found] ` <a5e0da9289019cce511d45c8eafa61f0@polymtl.ca>
2017-04-20 17:04 ` Simon Marchi
2017-04-20 17:17 ` Luke Dalessandro
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=F24E67E5-CC2F-45E5-9833-C6476B683B83@gmail.com \
--to=ldalessandro@gmail.com \
--cc=gdb@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