Re: Valgrind problem

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



On 24/10/07 06:54PM, Frank wrote:
> Good evening,

Hey Frank,

> I'm trying to debug an issue with Evolution and the Gnome guys asked me
> to use valgrind. However, when running this command I get an error I'm
> stuck with:
> valgrind --num-callers=30 --leak-check=no --track-origins=yes
> /usr/lib/evolution-calendar-factory -w

I had a quick look at this on my local machine, but could not get the
same debugging setup to work (for me the command just did nothing, so I
assume more setup is needed). Are you getting this issue when you also
set "--enable-debuginfod=yes" (which should be on by default) while
before doing a "export DEBUGINFOD_URLS='https://debuginfod.archlinux.org'"?

The debuginfod URL should also be set by default via
/etc/profile.d/debuginfod.sh which is installed via libelf.

If all that does not help mayb install the glibc debug package from your
nearest mirror:

    sudo pacman -U https://geo.mirror.pkgbuild.com/core-debug/os/x86_64/glibc-debug-2.40%2Br16%2Bgaa533d58ff-2-x86_64.pkg.tar.zst

Would be cool to get an update later on if things worked out or didn't
work :)

Cheers,
Chris

> ==4915== Memcheck, a memory error detector
> ==4915== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et
> al.
> ==4915== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright
> info
> ==4915== Command: /usr/lib/evolution-calendar-factory -w
> ==4915== 
> 
> 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:      strcmp
> valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
> valgrind:  was not found whilst processing
> valgrind:  symbols from the object with soname: ld-linux-x86-64.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:  Note that if you are debugging a 32 bit process on a
> valgrind:  64 bit system, you will need a corresponding 32 bit
> debuginfo
> valgrind:  package (e.g. libc6-dbg:i386).
> valgrind:  
> valgrind:  Cannot continue -- exiting now.  Sorry.
> 
> THX Frank
> 

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux