On Tue, 15 Dec 2020 12:18:57 +0000 David Osborne <da...@qcode.co.uk> wrote:
> So I have *removed* DSYSTEM_MALLOC from the default build flags and created > a new build... so far I've not been able to get that to crash in test > (where-as it was crashing every 3-4 requests when built with > DSYSTEM_MALLOC) If it does not crash with system malloc, the problem is just "masked-away" and may (or may not) re-appear at some other place/time. The only right way is to locate the culprit. But this can be a daunting task... If you want to debug it, the best way is to use the regular system malloc, turn-on any/all possible debug features of it (or of the compiler) and have a debugger attached to the process all the time, until it breaks. At that point, a stack trace may point you in the (potentially) right direction (or may not, depending on luck or lack-of thereof)... Alternatively, if running on Linux, a valgrind session may also be helpful. If the problem is reproducible (which most of the such problems are not) then it is easier... _______________________________________________ naviserver-devel mailing list naviserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/naviserver-devel
