Control: severity -1 grave Raising to grave, because as soon as the system is slightly loaded (e.g. executing a "configure" script), atop fails.
On 2018-11-17 10:42:36 +0100, Marc Haber wrote: > If this is a repeat occurrence, I don't have the slightest idea what > might be happening here other than asking you to try running atop with > debug info and trying to obtain a backtrace. Unfortunately, this is not possible. Perhaps with gdb and a breakpoint at this error message, but this might be too late. Or rebuilding atop with -fsanitize=undefined -fno-sanitize-recover would allow one to see where the problem occurs, since one can get a negative value: Malloc failed for -11968 exited processes probably as the cause of some undefined behavior. > I have not seen this on any of my systems. I can reproduce this problem on at least 2 machines. -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
