libpthread.so.2 compatibility
Daniel Eischen
deischen at freebsd.org
Sun Jun 4 23:05:14 UTC 2006
On Sun, 4 Jun 2006, John Hay wrote:
> On Sun, Jun 04, 2006 at 02:26:51PM -0400, Daniel Eischen wrote:
>> On Sun, 4 Jun 2006, John Hay wrote:
>>
>>> Actually one does not even need a big complex app to see the problem.
>>> Just copy /sbin/ggatec from 6.1 or 6.1-stable to a current box and you
>>> will see it happen:
>>>
>>> #######
>>> angel:~ > uname -a
>>> FreeBSD angel.cids.org.za 7.0-CURRENT FreeBSD 7.0-CURRENT #2: Sun May 28
>>> 11:06:16 SAST 2006
>>> jhay at angel.cids.org.za:/usr/src/sys/i386/compile/ANGEL i386
>>> angel:~ > ssh zibbi "uname -a"
>>> FreeBSD zibbi.meraka.csir.co.za 6.1-STABLE FreeBSD 6.1-STABLE #4: Thu May
>>> 25 06:11:44 SAST 2006
>>> jhay at zibbi.meraka.csir.co.za:/usr/src/sys/i386/compile/ZIBBI i386
>>> angel:~ > scp -p zibbi:/sbin/ggatec /tmp/
>>> ggatec 100% 16KB 8.1KB/s 00:02
>>> angel:~ > /tmp/ggatec
>>> Segmentation fault (core dumped)
>>> #######
>>
>> It is probably the networking ABI changes in libc. There was a short period
>> of time when there were ABI changes in libc.so.6 in -current -- before libc
>> was bumped to libc.so.7. What happens when you try moving a -stable
>> libc.so.6
>> to the -current machine?
>
> Ok, I did that but it still core dump in pthread_setcancelstate()
I don't know then. If recompiling it fixes the problem, then
something in /usr/include changed. All the pthread_foo_t types
are pointers to things allocated by the library, and I don't
think any of them changed anyways.
--
DE
More information about the freebsd-current
mailing list