[uClibc 0002264]: pthread issues with 0.9.29

bugs at busybox.net bugs at busybox.net
Thu Apr 3 16:51:34 UTC 2008


A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=2264 
====================================================================== 
Reported By:                kannappan
Assigned To:                uClibc
====================================================================== 
Project:                    uClibc
Issue ID:                   2264
Category:                   Posix Threads
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             02-20-2008 03:29 PST
Last Modified:              04-03-2008 09:51 PDT
====================================================================== 
Summary:                    pthread issues with 0.9.29
Description: 
I am using uclibc0.9.29, binutils 2.18 for ARM926T
I am facing problems executing applications which uses pthread.
when including pthread library my application crashes giving message
"segmentation fault". But the same is working with glibc .

When I debugged using strace It gave following error message

# strace  ./run_loop
execve("./run_loop", ["./run_loop"], [/* 16 vars */]) = -1 ENOEXEC (Exec
format
error)
write(2, "strace: exec: Exec format error\n", 32strace: exec: Exec format
error
) = 32
exit(1)                                 = ?
Process 738 detached

====================================================================== 

---------------------------------------------------------------------- 
 carmelo73 - 02-20-08 04:40  
---------------------------------------------------------------------- 
>From your output there is no evidence of a segfault. Please provide more
information.
Command line used to build your application. Source code if available.
Further I suggest you to build with debug synmbol (both your application
and uclibc) and start using gdb to debug.
The info you provide are not enough to figure out what is going wrong 

---------------------------------------------------------------------- 
 kannappan - 02-22-08 00:06  
---------------------------------------------------------------------- 
The problem happens when -lpthread is used along with -lc.

for example:

# arm-linux-gcc -lc -lpthread sample.c 

The strace for this attached.

The same program works when i compile with
# arm-linux-gcc -lpthread sample.c 

---------------------------------------------------------------------- 
 carmelo73 - 02-22-08 00:13  
---------------------------------------------------------------------- 
As a general suggestion, you don't need to link explicitly against libc
(-lc)...
it is done by default by the compiler (append -v at your build command and
you will see what it is doing silently)
Further are you sure arm-linux-gcc is properly configured for uClibc ?
Could you post the output of the command readelf -l <executable> ? 

---------------------------------------------------------------------- 
 vapier - 02-22-08 17:25  
---------------------------------------------------------------------- 
straces are not terribly useful when talking about a threading crash

please post a source code test case which we can compile/debug 

---------------------------------------------------------------------- 
 kannappan - 02-28-08 02:32  
---------------------------------------------------------------------- 
Following is the output of readelf

[kans at localhost test]$ arm-linux-readelf -l a.out 

Elf file type is EXEC (Executable file)
Entry point 0x83ac
There are 5 program headers, starting at offset 52

Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  PHDR           0x000034 0x00008034 0x00008034 0x000a0 0x000a0 R E 0x4
  INTERP         0x0000d4 0x000080d4 0x000080d4 0x00014 0x00014 R   0x1
      [Requesting program interpreter: /lib/ld-uClibc.so.0]
  LOAD           0x000000 0x00008000 0x00008000 0x0050c 0x0050c R E
0x8000
  LOAD           0x00050c 0x0001050c 0x0001050c 0x000ec 0x00108 RW 
0x8000
  DYNAMIC        0x000518 0x00010518 0x00010518 0x000c0 0x000c0 RW  0x4

 Section to Segment mapping:
  Segment Sections...
   00     
   01     .interp 
   02     .interp .hash .dynsym .dynstr .rel.plt .init .plt .text .fini
.rodata .eh_frame 
   03     .init_array .fini_array .jcr .dynamic .got .data .bss 
   04     .dynamic 

Following are the output when compiled with -v option

Using built-in specs.
Target: arm-linux-uclibcgnueabi
Configured with:
/data/buildroot/buildroot/toolchain_build_arm/gcc-4.1.2/configure
--prefix=/data/buildroot/buildroot/build_arm/staging_dir
--build=i386-pc-linux-gnu --host=i386-pc-linux-gnu
--target=arm-linux-uclibcgnueabi --enable-languages=c,c++
--disable-__cxa_atexit --enable-target-optspace --with-gnu-ld
--enable-shared --disable-nls --enable-threads --disable-multilib
--with-float=soft
Thread model: posix
gcc version 4.1.2

/data/buildroot/buildroot/build_arm/staging_dir/libexec/gcc/arm-linux-uclibcgnueabi/4.1.2/cc1
-quiet -v sample.c -quiet -dumpbase sample.c -mfloat-abi=soft -auxbase
sample -version -o /tmp/ccESRQ7x.s
ignoring nonexistent directory
"/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/include"
#include "..." search starts here:
#include <...> search starts here:

/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/include

/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/sys-include
End of search list.
GNU C version 4.1.2 (arm-linux-uclibcgnueabi)
        compiled by GNU C version 3.4.6 20060404 (Red Hat 3.4.6-8).
GGC heuristics: --param ggc-min-expand=64 --param ggc-min-heapsize=64298
Compiler executable checksum: 38e7075577afcde72725d9029281c4bb

/data/buildroot/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibcgnueabi-as
-mfloat-abi=soft -meabi=4 -o /tmp/ccW0JqfY.o /tmp/ccESRQ7x.s

/data/buildroot/buildroot/build_arm/staging_dir/libexec/gcc/arm-linux-uclibcgnueabi/4.1.2/collect2
--eh-frame-hdr -dynamic-linker /lib/ld-uClibc.so.0 -X -m armelf_linux_eabi
/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/lib/crt1.o
/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/lib/crti.o
/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/crtbegin.o
-L/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2
-L/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/lib
/tmp/ccW0JqfY.o -lpthread -lgcc --as-needed -lgcc_s --no-as-needed -lc
-lgcc --as-needed -lgcc_s --no-as-needed
/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/crtend.o
/data/buildroot/buildroot/build_arm/staging_dir/lib/gcc/arm-linux-uclibcgnueabi/4.1.2/../../../../arm-linux-uclibcgnueabi/lib/crtn.o


---------------------------------------------------------------------- 
 xi - 03-26-08 14:55  
---------------------------------------------------------------------- 
This is very similar to what I encountered with our MIPS toolchain and
NPTL. 0002414 might be the same problem too. 

I found one potential cause:

- Once libpthread is linked, standard loader is used instead of uClibc
loader


Here is a console log showing this problem with ldd:

$
/opt/toolchains/uclibc-crosstools-gcc-4.2.1-7/usr/bin/mips-linux-uclibc-gcc
-o test testc.o
/opt/toolchains/uclibc-crosstools-gcc-4.2.1-7/usr/bin/mips-linux-uclibc-ldd
test
checking sub-depends for 'not found'
        libc.so.0 => not found (0x00000000)
        <b>/lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)</b>


/opt/toolchains/uclibc-crosstools-gcc-4.2.1-7/usr/bin/mips-linux-uclibc-gcc
-o test testc.o –lpthread
$
/opt/toolchains/uclibc-crosstools-gcc-4.2.1-7/usr/bin/mips-linux-uclibc-ldd
test
checking sub-depends for '/lib/libpthread.so.0'
checking sub-depends for 'not found'
checking sub-depends for '/lib/libc.so.6'
        libpthread.so.0 => /lib/libpthread.so.0 (0x00000000)
        libc.so.0 => not found (0x00000000)
        libc.so.6 => /lib/libc.so.6 (0x00000000)
        <b>/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)</b>
$

 

---------------------------------------------------------------------- 
 bla - 04-02-08 01:38  
---------------------------------------------------------------------- 
I have the same issue on arm (nommu), uclibc 0.9.29. Using gdb on the
target I have tracked the problem down to the call to
__pthread_initialize_minimal during init. The call takes place via some
memory lookup, but ends up in the wrong place (somewhere in the data
segment). If I look at the target code with objdump -x I see this
disturbing fact:

00000000  w      *UND*  00000000 __pthread_initialize_minimal

So it's no wonder the call goes wrong, because the function code is not
included. It seems to me that something in the link process must have gone
wrong. The linker has clearly filled out the memory locations used in the
call with something, but forgot to include the actual code.

This is the part of the code where I see the failure (objdump -d):

00000898 <__GI___uClibc_init>:
     898:       e92d4010        stmdb   sp!, {r4, lr}
     89c:       e59f4054        ldr     r4, [pc,
http://busybox.net/bugs/view.php?id=84]   ; 8f8
<__GI___uClibc_init+0x60>
     8a0:       e59f0054        ldr     r0, [pc,
http://busybox.net/bugs/view.php?id=84]   ; 8fc
<__GI___uClibc_init+0x64>
     8a4:       e08f4004        add     r4, pc, r4
     8a8:       e7943000        ldr     r3, [r4, r0]
     8ac:       e3530000        cmp     r3,
http://busybox.net/bugs/view.php?id=0  ; 0x0
     8b0:       18bd8010        ldmneia sp!, {r4, pc}
     8b4:       e59f3044        ldr     r3, [pc,
http://busybox.net/bugs/view.php?id=68]   ; 900
<__GI___uClibc_init+0x68>
     8b8:       e7941003        ldr     r1, [r4, r3]
     8bc:       e59f3040        ldr     r3, [pc,
http://busybox.net/bugs/view.php?id=64]   ; 904
<__GI___uClibc_init+0x6c>
     8c0:       e7942003        ldr     r2, [r4, r3]
     8c4:       e3a03001        mov     r3,
http://busybox.net/bugs/view.php?id=1  ; 0x1
     8c8:       e7843000        str     r3, [r4, r0]
     8cc:       e3510000        cmp     r1,
http://busybox.net/bugs/view.php?id=0  ; 0x0
     8d0:       e3a03a01        mov     r3,
http://busybox.net/bugs/view.php?id=4096       ; 0x1000
     8d4:       e5823000        str     r3, [r2]
     8d8:       11a0e00f        movne   lr, pc
     8dc:       11a0f001        movne   pc, r1                    
<---------- FAILS HERE!!!
     8e0:       e59f3020        ldr     r3, [pc,
http://busybox.net/bugs/view.php?id=32]   ; 908
<__GI___uClibc_init+0x70>
     8e4:       e0843003        add     r3, r4, r3
     8e8:       e3530000        cmp     r3,
http://busybox.net/bugs/view.php?id=0  ; 0x0
     8ec:       08bd8010        ldmeqia sp!, {r4, pc}
     8f0:       e8bd4010        ldmia   sp!, {r4, lr}
     8f4:       eafffe30        b       fffffa84 <_ebss+0xffffbaf4>
     8f8:       00001414        andeq   r1, r0, r4, lsl r4
     8fc:       000022b8        streqh  r2, [r0], -r8
     900:       0000002c        andeq   r0, r0, ip, lsr
http://busybox.net/bugs/view.php?id=32
     904:       00000044        andeq   r0, r0, r4, asr
http://busybox.net/bugs/view.php?id=32
     908:       ffffe4fc        undefined instruction 0xffffe4fc 

---------------------------------------------------------------------- 
 hank_le - 04-03-08 09:51  
---------------------------------------------------------------------- 
I am having a similar problem for an i586 target using uClibc-0.9.29,
binutils 2.18, and gcc 4.2.1.

I cross compile with the following :

export PATH_TO_BUILDROOT=/home/leinhos/src/buildroot
export
CC=$PATH_TO_BUILDROOT/build_i586/staging_dir/usr/bin/i586-linux-gcc
export LD=$PATH_TO_BUILDROOT/build_i586/staging_dir/usr/bin/i586-linux-ld
export CPPFLAGS=-I$PATH_TO_BUILDROOT/build_i586/staging_dir/usr/include
export LDFLAGS=-L$PATH_TO_BUILDROOT/build_i586/staging_dir/usr/lib
export PATH=$PATH:$PATH_TO_BUILDROOT/build_i586/staging_dir/usr/bin

and use the following makefile target line:

CFLAGS +=  -g -Wall
LIBS = -lpthread
OBJS =  ${SRCS:.c=.o}
vc_bridge: ${OBJS}
        ${CC} ${LIBS} -o $@ ${OBJS}

If I check the backtrace on the target, I see:

(gdb) set solib-absolute-prefix
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/
(gdb) file vc_bridge
Reading symbols from /home/leinhos/src/vc_bridge-cvs/vc_bridge...done.
(gdb) target remote 192.168.9.200:1111
Remote debugging using 192.168.9.200:1111
warning: Remote failure reply: E01
0xb7f758b0 in _start () from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/ld-uClibc.so.0
(gdb) cont
Continuing.

Program received signal SIGSEGV, Segmentation fault.
0xb7efc0a2 in memcpy () from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/libc.so.0
(gdb) bt
http://busybox.net/bugs/view.php?id=0  0xb7efc0a2 in memcpy () from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/libc.so.0
http://busybox.net/bugs/view.php?id=1  0xb7f13ddc in __libc_pthread_init ()
   from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/libc.so.0
http://busybox.net/bugs/view.php?id=2  0xb7f647f8 in
__pthread_initialize_minimal ()
   from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/libpthread.so.0
http://busybox.net/bugs/view.php?id=3  0xb7f13ed9 in __uClibc_init () from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/libc.so.0
http://busybox.net/bugs/view.php?id=4  0xb7f78393 in _dl_get_ready_to_run ()
   from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/ld-uClibc.so.0
http://busybox.net/bugs/view.php?id=5  0xb7f786a0 in ?? () from
/home/leinhos/src/buildroot/project_build_i586/nuwcmp/root/lib/ld-uClibc.so.0
http://busybox.net/bugs/view.php?id=6  0xbf94a590 in ?? ()
http://busybox.net/bugs/view.php?id=7  0xb7f75000 in ?? ()
http://busybox.net/bugs/view.php?id=8  0xbf94a674 in ?? ()
http://busybox.net/bugs/view.php?id=9  0xbf94a70c in ?? ()
http://busybox.net/bugs/view.php?id=10 0xbf94a704 in ?? ()
http://busybox.net/bugs/view.php?id=11 0xbf94a674 in ?? ()
http://busybox.net/bugs/view.php?id=12 0xb7f75000 in ?? ()
http://busybox.net/bugs/view.php?id=13 0x00000002 in ?? ()
http://busybox.net/bugs/view.php?id=14 0x00000000 in ?? ()

I don't have any problems with applications compiled without pthreads. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
02-20-08 03:29  kannappan      New Issue                                    
02-20-08 03:29  kannappan      Status                   new => assigned     
02-20-08 03:29  kannappan      Assigned To               => uClibc          
02-20-08 04:40  carmelo73      Note Added: 0005174                          
02-20-08 04:40  carmelo73      Status                   assigned => feedback
02-22-08 00:03  kannappan      File Added: a                                
02-22-08 00:06  kannappan      Note Added: 0005224                          
02-22-08 00:13  carmelo73      Note Added: 0005234                          
02-22-08 17:25  vapier         Note Added: 0005254                          
02-28-08 02:32  kannappan      Note Added: 0005494                          
02-28-08 02:34  kannappan      File Added: sample.c                         
03-26-08 14:48  xi             Note Added: 0006074                          
03-26-08 14:54  xi             Note Edited: 0006074                         
03-26-08 14:55  xi             Note Edited: 0006074                         
04-02-08 01:38  bla            Note Added: 0006314                          
04-03-08 09:51  hank_le        Note Added: 0006374                          
======================================================================




More information about the uClibc-cvs mailing list