Re: Bug#701832: doxygen consistently segfaults on kfreebsd-i386 when building opendnssec documentation
Hi,
On Wed, Feb 27, 2013 at 19:24:59 +0100, Ondřej Surý wrote:
> the doxygen segfaults on kfreebsd-i386 when building opendnssec
> package and it blocks it's transition from unstable to testing.
> [...]
> https://buildd.debian.org/status/logs.php?arch=kfreebsd-i386&pkg=opendnssec&ver=1%3A1.3.9-4
It looks more like it's the 'dot' program from graphviz that hangs. I
ran its regression test suite repeatedly and managed to reproduce a
familiar thread-related hang in sigsuspend:
> steven 97235 0.0 0.1 83676 4436 ? T+ 12:03 0:00 /usr/bin/dot -Kdot -Tps -ondata/colors_dot.ps graphs/colors.gv
> (gdb) thread apply all bt full
>
> Thread 1 (process 97235):
> #0 __pthread_sigsuspend () at ../ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/linuxthreads/pt-sigsuspend.S:24
> No locals.
> #1 0x00000008038983b8 in __pthread_wait_for_restart_signal (self=<optimized out>) at pthread.c:1291
> mask = {{__sigbits = {2, 0, 0, 0}, __bits = {2, 0, 0, 0}}}
> #2 0x000000080389a7b4 in suspend (self=<optimized out>) at restart.h:34
> No locals.
> #3 __pthread_alt_lock (lock=<optimized out>, self=0x1f) at spinlock.c:418
> oldstatus = 0
> newstatus = 140737488322416
> wait_node = {next = 0x1, thr = 0x800637d20, abandoned = 0}
> #4 0x0000000803898023 in *__GI___pthread_mutex_lock (mutex=0x800ff3240) at mutex.c:123
> self = <optimized out>
> #5 0x0000000800d21f2c in *__GI___libc_free (mem=<optimized out>) at malloc.c:3736
> ar_ptr = 0x800ff3240
> p = <optimized out>
> #6 0x0000000800844a79 in gvFreeContext () from /usr/lib/libgvc.so.5
> No symbol table info available.
> #7 0x0000000000400fd8 in ?? ()
> No symbol table info available.
> #8 0x000000080389bf04 in __pthread_sighandler (signo=0, _code=65542, _sg=0x0, ctx=0xffffffff80e9f000) at sighandler.c:39
> self = <optimized out>
> #9 0x00007ffffffff083 in ?? ()
> No symbol table info available.
> #10 0x000000080389be60 in ?? () at internals.h:545 from /lib/x86_64-kfreebsd-gnu/libpthread.so.0
> No symbol table info available.
> #11 0x0000000000000000 in ?? ()
> No symbol table info available.
> (gdb)
Regards,
--
Steven Chamberlain
steven@pyro.eu.org
Reply to: