From: Luke Dalessandro <ldalessandro@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb@sourceware.org
Subject: Re: internal-error inferior_thread(): Assertion `tp' failed
Date: Thu, 20 Apr 2017 17:17:00 -0000 [thread overview]
Message-ID: <9C09E7F9-E934-450A-9EF2-AF0F57FE295B@gmail.com> (raw)
In-Reply-To: <4a2461e59c3e7528b9d8cb138829fa5f@polymtl.ca>
> On Apr 20, 2017, at 1:04 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
>
> I have just tried building Valgrind, and it runs fine for me with Valgrind-3.13.0.SVN. Some more data points:
>
> 1. g++/libstdc++/libc version? And which distro/version, that might be easier.
> 2. Does it still happen if you start gdb with -nx (to avoid loading any custom configuration)?
>
> Simon
I opened a bug for this https://sourceware.org/bugzilla/show_bug.cgi?id=21405.
1. gcc is 6.3
2. valgrind is svn(r16308) configured with `--enable-ubsan --with-mpicc=mpicc`
3. distribution is Ubuntu 14.04.5 LTS
4. -nx has no apparent impact
$ ldd hello
linux-vdso.so.1 => (0x00007ffc6f5db000)
libstdc++.so.6 => /u/ldalessa/.local/gcc/gcc-6.3/lib64/libstdc++.so.6 (0x00007fc89b245000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc89af3f000)
libgcc_s.so.1 => /u/ldalessa/.local/gcc/gcc-6.3/lib64/libgcc_s.so.1 (0x00007fc89ad28000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fc89ab0a000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc89a742000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc89b5c3000)
prev parent reply other threads:[~2017-04-20 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 14:13 Luke Dalessandro
[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 [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=9C09E7F9-E934-450A-9EF2-AF0F57FE295B@gmail.com \
--to=ldalessandro@gmail.com \
--cc=gdb@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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