Re: libqalculate FTBFS on mips* (ball, rem)
Julien BLACHE wrote:
> Martin Waitz <firstname.lastname@example.org> wrote:
> >> I can't take a deeper look at that right now, but I can give you a
> >> shell on the machine if you want.
> > thanks for your help!
> > A shell would be nice indeed.
> In the meantime, I've rebuilt cln at -O0 and the segfault still
> happens, although not at the same place.
> As some architectures have the asm parts disabled, I tried that too,
> but it still segfaults. Again at a different place.
I get consistently a segfault very early on startup (before __start is
hit) for any program linked with libcln (adding -lcln is enough):
Starting program: /home/ths/colo/libqalculate-0.8.1.1/clntest
Program received signal SIGSEGV, Segmentation fault.
0x2ab2000c in cln::cl_heap_weak_hashtable_1<cln::cl_rcpointer, cln::cl_rcpointer>::garcol () from /usr/lib/libcln.so.3
#0 0x2ab2000c in cln::cl_heap_weak_hashtable_1<cln::cl_rcpointer, cln::cl_rcpointer>::garcol () from /usr/lib/libcln.so.3
#1 0x00000008 in ?? ()
warning: GDB can't find the start of the function at 0x8.
GDB is unable to find the start of the function at 0x8
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
However, if you think GDB should simply search farther back
from 0x8 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
Previous frame inner to this frame (corrupt stack?)
This looks like the library tries to garbage collect from a global
constructor while the data it works on is still NULL.