Bug#807756: gnubg: fails to start. hangs using 100% of one cpu core
Russ Allbery
rra at debian.org
Sun Dec 13 23:56:42 UTC 2015
Control: reassign -1 gcc-5.0
Control: severity -1 important
Andreas Metzler <ametzler at bebt.de> writes:
> Some more points of strangeness:
> jessie's gnubg package (1.04.000-1) works on current stretch.
> Rebuilding the jessie source on current sid produces a binary which
> fails.
> Rebuilding with DEB_BUILD_OPTIONS=noopt works
> Rebuilding on current sid with gcc-4.9 produces a working package.
> Rebuilding either the jessie or the sid source with -O1 segfaults at
> start:
> (gdb) run
> Starting program: /usr/games/gnubg
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
> Program received signal SIGSEGV, Segmentation fault.
> memcpy (__dest=0x833070,
> __dest at entry=<error reading variable: DWARF-2 expression error: Loop detected (257).>, __src=0x7fffea09a46e,
> __src at entry=<error reading variable: DWARF-2 expression error: Loop detected (257).>, __len=6,
> __len at entry=<error reading variable: DWARF-2 expression error: Loop detected (257).>) at /usr/include/x86_64-linux-gnu/bits/string3.h:53
> 53
Hrm. Okay, so the compiler is doing something weird, and this isn't a
problem with libtasn1. Thanks for the additional information! I'm going
to reassign this to gcc-5, and might upload a package built explicitly
with gcc-4.9 as a workaround.
--
Russ Allbery (rra at debian.org) <http://www.eyrie.org/~eagle/>
More information about the Pkg-gnutls-maint
mailing list