From: "Ludovic Courtès" <ludo@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: help-guix@gnu.org
Subject: Re: Valgrind not working
Date: Tue, 08 Mar 2022 11:12:43 +0100 [thread overview]
Message-ID: <874k4892hw.fsf@gnu.org> (raw)
In-Reply-To: <Yebw9J9Nd2H6XUpJ@jurong> (Andreas Enge's message of "Tue, 18 Jan 2022 17:55:16 +0100")
Hi Andreas,
Andreas Enge <andreas@enge.fr> skribis:
> 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-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.
I’m late to the party, but here’s the trick you can use:
--8<---------------cut here---------------start------------->8---
$ guix build -e '(@@ (gnu packages commencement) glibc-final)'
/gnu/store/xgarlnscgbm9l04karj15xpc4nn14ak1-glibc-2.33-debug
/gnu/store/5h2w4qi9hk1qzzgi1w83220ydslinr4s-glibc-2.33
/gnu/store/4jdghmc65q7i7ib89zmvq66l0ghf7jc4-glibc-2.33-static
$ valgrind --extra-debuginfo-path=/gnu/store/xgarlnscgbm9l04karj15xpc4nn14ak1-glibc-2.33-debug/lib/debug uname -o
==16741== Memcheck, a memory error detector
==16741== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==16741== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==16741== Command: uname -o
==16741==
GNU/Linux
==16741==
==16741== HEAP SUMMARY:
==16741== in use at exit: 0 bytes in 0 blocks
==16741== total heap usage: 2,813 allocs, 2,813 frees, 184,302 bytes allocated
==16741==
==16741== All heap blocks were freed -- no leaks are possible
==16741==
==16741== For lists of detected and suppressed errors, rerun with: -s
==16741== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
--8<---------------cut here---------------end--------------->8---
I think the reason it no longer works out of the box is because we
now[*] use ‘--strip-unneeded’ instead of ‘--strip-debug’, since commit
e0f31baacc6ad30096a332b69433c85f5830bb2c.
We’d need to double-check the hypothesis and fix it on ‘core-updates’.
In the meantime, HTH!
Ludo’.
[*] Effective end of December 2021, when ‘core-updates’ was merged into
‘master’.
next prev parent reply other threads:[~2022-03-08 10:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 16:55 Valgrind not working Andreas Enge
2022-03-08 10:12 ` Ludovic Courtès [this message]
2022-09-02 15:28 ` Valgrind not working [core-update fixes?] zimoun
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=874k4892hw.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=help-guix@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.