From: "Jürgen Beisert" <jbe@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: jon.bird@generaldynamics.uk.com
Subject: Re: [ptxdist] How to get valgrind working in ptx build
Date: Wed, 7 Aug 2013 15:10:58 +0200 [thread overview]
Message-ID: <201308071510.58228.jbe@pengutronix.de> (raw)
In-Reply-To: <94D4A88F8AC34646A5288D11318F5D5B0D723E9F@GDUKADH841.uk1.r-org.net>
Hi Jon,
On Wednesday 07 August 2013 14:32:50 jon.bird@generaldynamics.uk.com wrote:
> I am trying to get valgrind enabled under Ptxdist. I can build the package
> ok and deploy it however when I attempt to run an app on the target system
> it fails complaining that it needs debugging symbols from glibc. The
> suggesion from online is that I either need a non-stripped glibc or an
> additional file which holds the symbols but it isn't clear from online
> searching what this file is called or where to locate it in the file
> system. The toolchain I am using is the OSELAS.Toolchain-2012.12.1 x86
> toolchain (prebuilt Debian package), I am hoping I just need to lift the
> relevant file(s) from there.
Sounds like you need to boot via network (NFSroot) and need to use
the "root-debug" directory instead of the "root" one as the root filesystem.
"root-debug" still contains all debug info.
Debug info for the main glibc is a different issue. This would drastically
increase the binary, so it is disabled by default.
When building the toolchain you can enable a special menu entry to keep the
debug info also for glibc (read its help!):
ptxdist menuconfig
misc --->
[*] debuggable toolchain internals
Regards,
Juergen
--
Pengutronix e.K. | Juergen Beisert |
Linux Solutions for Science and Industry | http://www.pengutronix.de/ |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-08-07 13:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 12:32 jon.bird
2013-08-07 13:04 ` Marc Kleine-Budde
2013-08-07 13:10 ` Jürgen Beisert [this message]
2013-08-07 13:47 ` jon.bird
2013-08-07 14:20 ` Marc Kleine-Budde
2013-08-08 9:21 ` jon.bird
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=201308071510.58228.jbe@pengutronix.de \
--to=jbe@pengutronix.de \
--cc=jon.bird@generaldynamics.uk.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