Fixed
Created: May 15, 2015
Updated: Dec 3, 2018
Resolved Date: Jun 12, 2015
Found In Version: 6.0.0.19
Severity: Standard
Applicable for: Wind River Linux 6
Component/s: Toolchain
Our customer is facing the bug described in https://bugzilla.redhat.com/show_bug.cgi?id=593396
He claims this fixes his issue:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8b43a2274a593ce91e673db1cfac6e808134bc84
Could we integrate the fix?
1) Configure a project with
--with-template=feature/build_libc
2) make -C build eglibc-sourcery-compile.patch
3) cd build/eglibc-sourcery-compile/glibc-2.*
4) patch -Np1 < /path-of-attached-patch
5) cd ../../..
6) make fs fs-debug
--------------
To verify the issue without and with the patch,
1) compile the test code
$CC -g -O0 atomic_free.c -pthread -o atomic_free
2) add gdb to the target
make -C build gdb.addpkg
make fs fs-debug
3) copy the binary and gdb script to target, launch it, and
gdb ./atomic_free -x gdb_script
Segmentation fault should happen w/o the patch.
Notice that after the patch, the line where breakpoint should be placed is changed, so use gdb_script_fix to verify the fixed glibc.
--------------------
