From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mail1.bemta3.messagelabs.com ([195.245.230.161]) by metis.ext.pengutronix.de with esmtp (Exim 4.72) (envelope-from ) id 1V745V-0001k3-FA for ptxdist@pengutronix.de; Wed, 07 Aug 2013 15:47:43 +0200 From: Date: Wed, 7 Aug 2013 13:47:38 +0000 Message-ID: <94D4A88F8AC34646A5288D11318F5D5B0D723F32@GDUKADH841.uk1.r-org.net> References: <94D4A88F8AC34646A5288D11318F5D5B0D723E9F@GDUKADH841.uk1.r-org.net> <201308071510.58228.jbe@pengutronix.de> In-Reply-To: <201308071510.58228.jbe@pengutronix.de> Content-Language: en-US MIME-Version: 1.0 Subject: Re: [ptxdist] How to get valgrind working in ptx build Reply-To: ptxdist@pengutronix.de List-Id: PTXdist Development Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: ptxdist-bounces@pengutronix.de Errors-To: ptxdist-bounces@pengutronix.de To: ptxdist@pengutronix.de Thanks for the replies, On 07 August 2013 14:11, J=FCrgen Beisert wrote: > 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 > = I'll give the nfs-root thing a go but from what you've said it sounds like = I need to rebuild the toolchain with debugging enabled. Rgs, Jon. This email and any files attached are intended for the addressee and may co= ntain information of a confidential nature. If you are not the intended rec= ipient, be aware that this email was sent to you in error and you should no= t disclose, distribute, print, copy or make other use of this email or its = attachments. Such actions, in fact, may be unlawful. In compliance with the= various Regulations and Acts, General Dynamics United Kingdom Limited rese= rves the right to monitor (and examine for viruses) all emails and email at= tachments, both inbound and outbound. Email communications and their attach= ments may not be secure or error- or virus-free and the company does not ac= cept liability or responsibility for such matters or the consequences there= of. General Dynamics United Kingdom Limited, Registered Office: 21 Holborn = Viaduct, London EC1A 2DY. Registered in England and Wales No: 1911653. = -- = ptxdist mailing list ptxdist@pengutronix.de