Harri Haataja wrote:
Funny. How do these things look:
Sorry for my late response; yesterday I touched the laptop again, and
saw your message after googling.
I'll instead show the tcc compiled tcc version;
file test
file ./tcc
./tcc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), not stripped
gcc linked:
file /usr/bin/tcc
/usr/bin/tcc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), stripped
ldd test
ldd ./tcc
checking sub-depends for '/lib/libm.so.0'
libc.so.0 => /lib/libc.so.0 (0xb7f92000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb7fe3000)
checking sub-depends for '/lib/libc.so.0'
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb7f8a000)
checking sub-depends for '/lib/libdl.so.0'
libc.so.0 => /lib/libc.so.0 (0xb7f46000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb7f97000)
libm.so.0 => /lib/libm.so.0 (0x00000000)
libc.so.0 => /lib/libc.so.0 (0x00000000)
libdl.so.0 => /lib/libdl.so.0 (0x00000000)
/lib/ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0x00000000)
gcc linked:
ldd /usr/bin/tcc
libm.so.0 => /lib/libm.so.0 (0xb7f8f000)
libdl.so.0 => /lib/libdl.so.0 (0xb7f8b000)
libc.so.0 => /lib/libc.so.0 (0xb7f3f000)
ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb7fa3000)
ls -l test
-rwxr-xr-x 1 root root 399916 Mar 6 00:09 ./tcc
-rwxr-xr-x 1 root root 128816 Mar 6 00:09 /usr/bin/tcc
You could try running that in a debugger to see more about the segfault.
I'll try to compile gdb; but I have another observation. It does not
seem that tcc creates broken object files. For example I can compile
something to .o when linked using gcc I end up with a working binary.
Stefan
_______________________________________________
Tinycc-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/tinycc-devel
