Segfaults on across the board in TH

[Caleb Maclennan]

> I have reported this problem long time ago on a polish devel list. There was
> no solution given (only "we must wait for the next nvidia release") and I've
> switched to nv. Then pluto suggested to try:

I started seeing this with a 290.x nvidia driver version and never
figured it out, but I've waited to whine about it until 295.x came to
TH and I'm seeing the same problem. There has to be a better answer. I
have nvidia drivers on other distros and it's not doing this. What is
different?

> valgrind --tool=helgrind glxinfo

I'm attaching my output from this ... honestly it doesn't tell me much.

Caleb
-------------- next part --------------
==7959== Helgrind, a thread error detector
==7959== Copyright (C) 2007-2011, and GNU GPL'd, by OpenWorks LLP et al.
==7959== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==7959== Command: glxinfo
==7959== 
--7959-- WARNING: Serious error when reading debug info
--7959-- When reading debug info from /usr/lib/nvidia/libGL.so.295.20:
--7959-- Can't make sense of .got.plt section mapping
--7959-- WARNING: Serious error when reading debug info
--7959-- When reading debug info from /usr/lib/nvidia/libnvidia-glcore.so.295.20:
--7959-- Can't make sense of .got section mapping

Helgrind: hg_main.c:4273 (is_in_dynamic_linker_shared_object): Assertion 'soname' failed.
==7959==    at 0x380337AB: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3803390F: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3801D589: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3804B645: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x380D1E62: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3804DF40: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3807B1D7: ??? (in /usr/lib/valgrind/helgrind-x86-linux)
==7959==    by 0x3808C31C: ??? (in /usr/lib/valgrind/helgrind-x86-linux)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==7959==    at 0x484B1C9: ??? (in /usr/lib/nvidia/libnvidia-glcore.so.295.20)
==7959==    by 0x484B0D8: ??? (in /usr/lib/nvidia/libnvidia-glcore.so.295.20)
==7959==    by 0x400F00C: call_init (in /lib/ld-2.15.so)
==7959==    by 0xBEE494A6: ???
==7959==    by 0x49444E44: ???


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.