On 2018-11-19 09:58:04 +0100, Vincent Lefevre wrote: > 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.
I've put abort()'s, but indeed, that's too late to get meaningful information. > 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've done that, but then, I can't reproduce the problem! It might be due to a compiler bug, or because the code is too slow in this case. -- 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)
