Re: OOo fails to build with glibc 2.5 in Debian (on sparc)
I just saw these idlc hangs for the first time building OOF680_m15 with
gcc-3.3
I built o208 a couple of days ago with gcc-4.1.2 and m14 with gcc-3.3 2
weeks ago.
same kernel on sid each time, no problem seen then.
jim@sun:~$ uname -a
Linux sun 2.6.18-4-sparc64 #1 Mon Mar 26 11:16:07 UTC 2007 sparc64
GNU/Linux
$ps ax
6838 pts/3 S+ 0:01 perl /home/jim/vanilla/solenv/bin/build.pl
--all:offapi
11002 pts/3 S+ 0:00 dmake
11232 pts/3 S+ 0:00 -usr/bin/tcsh -fc idlc @/tmp/mk3ZDQrV
11233 pts/3 Sl+ 0:00 idlc @/tmp/mk3ZDQrV
11263 pts/3 R+ 10:45 idlc @/tmp/mk3ZDQrV
top shows 11263 using 98% of cpu
$ gdb idlc 11233
0xf7cf7ef8 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
(gdb) bt
#0 0xf7cf7ef8 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/libpthread.so.0
#1 0xf7d6ea28 in osl_waitCondition ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#2 0xf7d73904 in osl_psz_executeProcess ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#3 0xf7d7354c in osl_executeProcess_WithRedirectedIO ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#4 0xf7d73624 in osl_executeProcess ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#5 0x0002a990 in compileFile ()
#6 0x000279d4 in sal_main_with_args ()
#7 0xf792e6cc in __libc_start_main () from /lib/libc.so.6
#8 0x0001acc8 in _start ()
(gdb)
$ gdb idlc 11263
0xf7cfb3ec in __pthread_enable_asynccancel () from /lib/libpthread.so.0
(gdb) bt
#0 0xf7cfb3ec in __pthread_enable_asynccancel () from /lib/libpthread.so.0
#1 0xf7cfbbd0 in ?? () from /lib/libpthread.so.0
#2 0xf7d72ed4 in ChildStatusProc ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#3 0xf7d71c6c in osl_thread_start_Impl ()
from /home/jim/vanilla/solver/680/unxlngs.pro/lib/libuno_sal.so.3
#4 0xf7cf16ec in start_thread () from /lib/libpthread.so.0
#5 0xf79e57a0 in ?? () from /lib/libc.so.6
#6 0xf79e57a0 in ?? () from /lib/libc.so.6
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)
Reply to: