On 5/30/2022 11:53 PM, Ulrich Windl wrote:
I wonder: Would forcing a core dump help in that situation, or would a gprof-compile be helpful?
Unfortunately I can't reproduce it; it just happens randomly on my production boxes, less frequently since I increased the amount of memory on them. I'm not sure I could run a debug or profiling build in production for an extended amount of time waiting for it to happen. And with my luck it would be a heisenbug anyway 8-/.
Maybe one could track down the page fault to some code (function) using tools from the valgrind family (Cachegrind, callgrind, etc.) http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.valgrind-monitor-commands
