On 17/03/13 22:50, Alan Robertson wrote: > Copious Spare Time or not - your packages are much appreciated!
Thanks! > If you had a stack trace that would be wonderful. That's a weird > message - because that means that that address has never been allocated > to any object before - or that I failed to tell the object system about > it. Usually it's a "use-after-free" problem. But ConfigValues aren't > first-class objects - so maybe that is somehow causing the problem. > Weird... If the nanoprobe is printing that message, then it crashed > too. The nanoprobe is _far_ more likely to produce a usable stack trace > than the python code in the CMA. Giving either one a -f option will > keep it in the foreground and keep it from forking - so you can run it > under gdb - which tends to give better results than looking at a core file. nanoprobe appears to be just mirroring the error message from cma, as it doesn't crash itself. nanoprobe seems to just carry on. Here are some logs: https://jamielinux.com/pub/stderr-nanoprobe.txt https://jamielinux.com/pub/strace-cma.txt https://jamielinux.com/pub/backtrace-cma.txt https://jamielinux.com/pub/strace-nanoprobe.txt https://jamielinux.com/pub/backtrace-nanoprobe.txt (Another odd thing is that both cma and nanoprobe output debug messages by default when on EPEL 6 even without passing "-d" option.) Kind regards, -- Jamie Nguyen _______________________________________________ Assimilation mailing list - Discovery-Driven Monitoring [email protected] http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation http://assimmon.org/
