From: "Crim, Jason" <jason.crim@thyssenkrupp.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc.
Date: Thu, 22 Mar 2018 12:38:21 -0500 [thread overview]
Message-ID: <2D79272AFFD75A4392ED2D3EF16D3B53A8943F@mdcxch20.na.ops.local> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2599 bytes --]
I'm currently using ptxdist 2015.10.0 and I've selected valgrind as a
built-in option in the 'Debug Tools' using menuconfig. Valgrind is then
installed in my image at /usr/bin/valgrind. However, it is currently
not usable since the available glibc is too optimized, resulting in the
following message.
>
> 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-armhf.so.3
> valgrind: was not found whilst processing
> valgrind: symbols from the object with soname:
ld-linux-armhf.so.3
> 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.
I've found a couple of references to the optimization being the culprit,
such as https://sourceforge.net/p/valgrind/mailman/message/30887009/
>
> ...
> Very probably these are due to calls on strlen() or
memcpy() which have been
> expanded inline because of aggressive optimization
("#include <string.h>"
> compiled with -O2 or -O3.)
> ...
Is there a method of configuring glibc to build un-optimized ( below
-O2) for use with the valgrind tool?
Can the valgrind selection automatically trigger this un-optimized
build?
Or, if there are other suggestions for addressing this issue, I'd like
to hear them.
Thanks,
- Jason Crim
[-- Attachment #1.2: Type: text/html, Size: 7404 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-03-22 17:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 17:38 Crim, Jason [this message]
2018-03-26 6:30 ` Michael Olbrich
2018-03-26 12:03 ` Crim, Jason
2018-03-27 7:33 ` Michael Olbrich
2018-03-27 11:54 ` Crim, Jason
2018-03-28 10:01 Andrej.Gantvorg
2018-03-28 15:43 ` Crim, Jason
2018-03-29 9:20 ` Michael Olbrich
2018-04-05 19:41 ` Crim, Jason
2018-04-09 8:41 ` Michael Olbrich
2018-04-09 12:13 ` Crim, Jason
2018-04-09 13:49 ` Michael Olbrich
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=2D79272AFFD75A4392ED2D3EF16D3B53A8943F@mdcxch20.na.ops.local \
--to=jason.crim@thyssenkrupp.com \
--cc=ptxdist@pengutronix.de \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox