Project Home
Project Home		 Source Code
Source Code		 File Releases
File Releases		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Valgrind/Discussion/General/Can't find libc.so.3 symbols/List of Posts
Forum Topic - Can't find libc.so.3 symbols: (4 Items)
   
Update
Mario Charest
02/21/2017 2:31 PM
post117436
Can't find libc.so.3 symbols   
On 650SP1 been trying to get valgrind to load symbols files for libc.so.3.  Before today I used raw option to leave the 
symbols in /proc/boot but this creates issues so we have to take the raw option out.  What ever I try to do I can't 
seems to get vlgrind to even search for it.  

Running with the same option as on the wiki page, it differs in that it does not seems to go through the search paths.  
Using --extra-debuginfo-path makes no difference.

Suggestions?

#:/tmp> QNX_TARGET=/ valgrind -v -v -v ls
==47526085== Memcheck, a memory error detector
==47526085== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==47526085== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==47526085== Command: ls
==47526085==
--47526085-- Valgrind options:
--47526085--    --tool=memcheck
--47526085--    -v
--47526085--    -v
--47526085--    -v
--47526085-- Contents of /proc/version:
--47526085--   can't open /proc/version
--47526085-- Arch and hwcaps: X86, LittleEndian, x86-mmxext-sse1-sse2-lzcnt
--47526085-- Page sizes: currently 4096, max supported 4096
--47526085-- Valgrind library directory: /usr/lib/valgrind
--47526085-- TT/TC: VG_(init_tt_tc) (startup of code management)
--47526085-- TT/TC: cache: 16 sectors of 27597024 bytes each = 441552384 total
--47526085-- TT/TC: table: 16 tables  of 11007528 bytes each = 176120448 total
--47526085-- TT/TC: table: 65521 entries each = 1048336 total entries max occupancy 681408 (65%)
--47526085-- Reading syms from /proc/boot/libc.so.3
--47526085--    svma 0x0000000000, avma 0x0000001000
--47526085-- No CRC or build-id in "/proc/boot/libc.so.3"
==47526085==
==47526085==
==47526085== Valgrind is exiting:
==47526085==   Symbols for /proc/boot/libc.so.3 are required but not found.
==47526085==   (Suggestion: compile that binary with debug-information, or provide a separate symbol-file.)
==47526085==
==47526085==
Michael Daniels(deleted)
02/21/2017 3:53 PM
post117437
Re: Can't find libc.so.3 symbols   
mkifs is a little aggressive and will strip off the build-id and debuglink sections.

Without one of these valgrind is not able to reliably tell if a symbol/debug file actually corresponds to the one being 
loaded.

One method is to use the raw attribute to avoid stripping libc, as you have been doing. You can also tell mkifs to leave
 certain sections alone with "-s <section>". If neither of these are options for you and you are positive you have the 
right files, you can start playing with fire and pass "--allow-mismatched-debuginfo=yes" to valgrind.
Mario Charest
02/21/2017 4:41 PM
post117438
Re: Can't find libc.so.3 symbols   
> mkifs is a little aggressive and will strip off the build-id and debuglink 
> sections.
> 
> Without one of these valgrind is not able to reliably tell if a symbol/debug 
> file actually corresponds to the one being loaded.
> 
> One method is to use the raw attribute to avoid stripping libc, as you have 
> been doing. You can also tell mkifs to leave certain sections alone with "-s <section>"
> . If neither of these are options for you and you are positive you have the 
> right files, 

Can't do that, tech support teels me that doing so (using raw attributes) prevents the shared object from being really 
shared, consume extra memory in the process, 

> you can start playing with fire and pass "--allow-mismatched-
> debuginfo=yes" to valgrind.

Got it, I have to use --allow-mismtched-debuginfo AND --extra-debuginfo-path.  It does not seems to be searching the 
default paths at all.

Thanks for pointing me in the right direction.
Matthew Falkoski(deleted)
03/28/2017 5:53 PM
post117566
Re: Can't find libc.so.3 symbols   
I running into this exact issue as well. Were you ever able to get it to work?

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems