| View previous topic :: View next topic |
| Author |
Message |
cwr
Veteran
Joined: 17 Dec 2005
Posts: 1969
|
 Posted: Sat Dec 28, 2013 2:31 pm Post subject: Valgrind and gcc [SOLVED] |
 |
|
Does anyone have a working pair of Valgrind/GCC versions, assuming that
splitdebug is set for glibc? I've tried a couple of combinations of versions,
and Valgrind blows up every time; there must surely be a way to get it to work?
(I've read the bug reports, and they don't seem hopeful.)
Will
Last edited by cwr on Sun Dec 29, 2013 2:07 pm; edited 1 time in total |
|
| Back to top |
|
 |
Hu
Moderator
Joined: 06 Mar 2007
Posts: 21631
|
| Posted: Sat Dec 28, 2013 4:57 pm Post subject: |
|
|
| I use an amd64 system with Valgrind 3.9.0, glibc 2.15 (FEATURES=nostrip), and various released gcc. I have not noticed any problems that I would characterize as "blowing up" on execution. You asked for splitdebug, but is there a reason you want that instead of nostrip? You can selectively build particular packages with FEATURES=nostrip, though it is admittedly inconvenient. |
|
| Back to top |
|
|
cwr
Veteran
Joined: 17 Dec 2005
Posts: 1969
|
| Posted: Sun Dec 29, 2013 2:06 pm Post subject: |
|
|
I used splitdebug (on glibc-2.15.-r3 only) because from reading the bug reports that seems to be the approved
way of fixing valgrind. As I understand it, valgrind looks for some symbols that recent versions of gcc optimise
away - on one of my older systems valgrind runs with no problems at all.
Anyway, glibc and splitdebug and the most recent testing version of valgrind now work, so that's something
accomplished. Quite what was broken and why I still don't understand.
Will |
|
| Back to top |
|
|
|
Portage & Programming
