Fwd: Bug#397489: gtimer: crashes at startup

[Russ Allbery <rra@debian.org>]

Please cc me on replies; I'm not subscribed to debian-powerpc.

Is there a PowerPC porter who could take a look at bug #397489?  The
current build of gtimer crashes on startup on PowerPC but works fine for
me on i386 and AMD64.  I suspect either some sort of compiler problem or
some sort of uninitialized variable, since running the binary under
valgrind or rebuilding it with -g3 causes it to not crash.  However,
running it under valgrind on x86 doesn't turn up anything that seems to be
caused by the package, just the normal noise from dlopen and NSS and some
from gtk.

The backtrace of the crash is unfortunately not particularly useful:

*** glibc detected *** free(): invalid pointer: 0x1006ab80 ***
Program received signal SIGABRT, Aborted.
0x0f9d07bc in raise () from /lib/tls/libc.so.6
(gdb) bt
#0  0x0f9d07bc in raise () from /lib/tls/libc.so.6
#1  0x0f9d22c0 in abort () from /lib/tls/libc.so.6
#2  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#3  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#4  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#5  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#6  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#7  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#8  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#9  0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#10 0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
#11 0x0fa0af60 in __fsetlocking () from /lib/tls/libc.so.6
Previous frame inner to this frame (corrupt stack?)
(gdb)

Also, let me know if there's something else that I should be checking or
can try to try to track this down; I'm not really sure how to approach the
problem.

-- 
Russ Allbery (rra@debian.org)               <http://www.eyrie.org/~eagle/>