This is the mail archive of the
mailing list for the glibc project.
Re: glibc 2.3 not binary compatible with glibc-2.2.5
- From: Christoph Lameter <christoph at lameter dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: Roland McGrath <roland at redhat dot com>, <libc-alpha at sources dot redhat dot com>
- Date: Sat, 5 Oct 2002 13:30:45 -0700 (PDT)
- Subject: Re: glibc 2.3 not binary compatible with glibc-2.2.5
On Sat, 5 Oct 2002, Daniel Jacobowitz wrote:
> Doesn't work. Then when gdb runs /bin/tar it will actually get
> The easiest way to fix this is to just make a chroot with GDB in it...
Ok here is the output from the chroot:
k2-400:/home/christoph/t# chroot . sbin/gdb /sbin/tar
GNU gdb 5.2.1
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i486-pc-linux-gnu"...
Starting program: /sbin/tar
[New Thread 16384 (LWP 3530)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 3530)]
0x401681a8 in __errno_location () from /lib/libpthread.so.0
#0 0x401681a8 in __errno_location () from /lib/libpthread.so.0
#1 0x40032abc in __timer_signal_thread_rclk () from /lib/libc.so.6
Now what else do you need to know?