Re: any suggestions to detect memory corruption

Alex <zhihui(dot)fan1213(at)gmail(dot)com> writes:
> I can get the following log randomly and I am not which commit caused it.

> 2019-05-08 21:37:46.692 CST [60110] WARNING: problem in alloc set index
> info: req size > alloc size for chunk 0x2a33a78 in block 0x2a33a18

I've had success in finding memory stomp causes fairly quickly by setting
a hardware watchpoint in gdb on the affected location. Then you just let
it run to see when the value changes, and check whether that's a "legit"
or "not legit" modification point.

The hard part of that, of course, is to know in advance where the affected
location is. You may be able to make things sufficiently repeatable by
doing the problem query in a fresh session each time.

regards, tom lane