Bug#304413: libc6: last update broke StarOffice52
At Wed, 13 Apr 2005 00:48:17 +0200,
Paolo wrote:
> well, SO5.2 is Debian-unrelated since there's no .deb for it, though it's
> related since it needs libc6. Whatever, it got broken, hope the Justification
> is ehm formally justified.
>
> I've been using SO 5.2 rather smoothly, till last update above, after which
> I get:
>
> ...
> (no debugging symbols found)
> (no debugging symbols found)
> [New Thread -1259529296 (LWP 6811)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1259529296 (LWP 6811)]
> 0xb567b9c1 in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
> (gdb) bt
> #0 0xb567b9c1 in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
> #1 0xb567bbda in osl_releaseMutex () from /usr/opt/office52/program/libsal1.so
> #2 0xb54edb63 in start_thread () from /lib/tls/libpthread.so.0
> #3 0xb546ac4a in clone () from /lib/tls/libc.so.6
> (gdb)
gdb said clone() system call which forks new thread worked correctly,
but the invoked thread routine in SO 5.2 did not work. It might be SO
5.2 specific problem.
> apt-get updated a number of .deb as usual, though I think libc6 is likely
> to blame. Tried and verified on 2 similar (Sarge) systems.
> SO 5.2 still works fine on Slackware 10.1 (libc-2.3.4).
Which libc6 version did you use?
If it's woody -> sarge problem, and if you have some knowledges to
create woody chroot environment with debootstrap, try to upgrade libc6
only from woody to sarge on chroot. Then invoke SO 5.2. Otherwise,
we cannot track down because SO 5.2 is not part of Debian packages.
If it's glibc problem, you can confirm whether this is 2.3.2.ds1
specific problem or not using libc6 2.3.4 in experimental.
Regards,
-- gotom
Reply to: