WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: valgrind doesn't work  (Read 368 times)

Offline jls

  • Hero Member
  • *****
  • Posts: 2028
    • Core17
valgrind doesn't work
« on: June 17, 2016, 01:18:32 PM »
Hi
Code: [Select]
jls@box:~$ enlightenment_start -display :1.0 -valgrind
E - PID=14834, valgrind=1 valgrind-command='/usr/bin/valgrind'
==14835== Memcheck, a memory error detector
==14835== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==14835== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==14835== Command: /tmp/tcloop/e20-terminology/usr/bin/enlightenment -display :1
.0 -valgrind
==14835==

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strlen
valgrind:  in an object with soname matching:   ld-linux.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux.so.2
valgrind:
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.  The package you need
valgrind:  to install for fix (1) is called
valgrind:
valgrind:    On Debian, Ubuntu:                 libc6-dbg
valgrind:    On SuSE, openSuSE, Fedora, RHEL:   glibc-debuginfo
valgrind:
valgrind:  Cannot continue -- exiting now.  Sorry.

jls@box:~$ grep libc6-dbg /tmp/.debinstalled
libc6-dbg:
jls@box:~$



An e devel wrote me this:
You can get a valgrind trace by running enlightenment under Xephyr. In a first console do :

$ Xephyr :1.0

In a second console do :

enlightenment_start -display :1.0 -valgrind

Then navigate to where it does trigger the crash and it should give you in the second console a better backtrace.
dCore user