On June 29, 2018 10:51:46 PM CDT, Bruce Dubbs <[email protected]> wrote:
>
>
>On 06/29/2018 10:12 PM, Ken Moffat wrote:
>> I'm trying to get the BLFS tests for libinput to run.  Among the
>> instructions is a commented hunk about valgrind needing debugging
>> symbols:
>>
>

<Snip>

>>
>> BUT running
>>
>>   ln -svf ld-2.27.so.dbg /lib/ld-linux-x86-64.so.2
>>
>> makes the system unusable (everything segfaults), the used tty
>> generates the old "respawning too fast" message (at least in
>> sysvinit).  Rebooting (Magic_SysRQ, otherwise a power interruption
>> would be required) fails to boot, init killed, kernel panic.


You broke it! :-)

>>
>I can't say right now Ken, but I'll start build ing a new BLFS in a
>few days and see if I can duplicate the problem.
>

No need (at least not for that). We changed this not too long ago. See the 
stripping page in LFS for a full explanation. In short, we used to keep a copy 
of the library that was not stripped. Now, using objcopy, we dump the debug 
symbols to a separate file for a handful of specific libraries that are always 
required to make debuging useful (libc, ld, gcc libs, etc.). The .dbg file is 
just the separate debuging symbols, not a library, and should load 
automatically. You can optionally get rid of them if you will never use 
valgrind or gdb. You can do the same with any other program built with -g. The 
corresponding .dbg file should either be in the same directory as the file that 
needs it, in a .debug subdirectory (relative to the file), or in /usr/lib/debug 
for autoloading to work correctly.

See the following links for better explanations:
 http://www.linuxfromscratch.org/lfs/view/development/chapter06/aboutdebug.html

http://www.linuxfromscratch.org/lfs/view/development/chapter06/strippingagain.html

https://www.technovelty.org/code/separate-debug-info.html

HTH

--DJ



-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to