Julien BLACHE wrote: > Thiemo Seufer <[EMAIL PROTECTED]> wrote: > > > I get consistently a segfault very early on startup (before __start is > > hit) for any program linked with libcln (adding -lcln is enough): > > > > > > (gdb) run > > 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 > > (gdb) bt > > #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. > > That's this one, indeed. Though I didn't realize it happened even > before __start. > > > This looks like the library tries to garbage collect from a global > > constructor while the data it works on is still NULL. > > Sounds like it, but is there a reason why it happens only on mips ?
I haven't seen anything mips-specific there. The compiler flags settings in cln's debian/rules don't exactly inspire confidence in the source code, same goes for the "filter out the -Os optimization to prevent segfaults" strategy in libqalculate. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
