yade-dev team mailing list archive

[Václav Šmilauer <eudoxos@xxxxxxxx>]

> Thread 1 (Thread 0x7f54c22f26f0 (LWP 3815)):
> #0  0x00007f54c1303299 in ?? () from /lib/libc.so.6
> #1  0x00007f54c130364c in system () from /lib/libc.so.6
> #2  0x00007f54c095d2d0 in crashHandler (sig=11) at core/main/pyboot.cpp:43
> #3  <signal handler called>
> #4  0x00000000019847e0 in ?? ()
> #5  0x00007f54ae92fe8e in ~ObjectPtrT (this=0x7f54c0b7d560) at /usr/include/log4cxx/helpers/objectptr.h:100
> #6  0x00007f54c12fa6ed in exit () from /lib/libc.so.6

Hi,

unrelated to NAG, it is a known bug in log4cxx and it should happen only 
when exiting Yade. We know about it 
https://bugs.launchpad.net/yade/+bug/410250 and it will be fixed if you 
disable log4cxx or once we switch to another logging library (there is 
one pending in boost).

HTH, Vaclav