Dump full memory maps around failing Windows reattach code.

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 6ba0cc4bd3a6d738eddf7e8aa2ef7b46cdd9ce8f
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2018-04-30T15:16:21Z
Releases: 11.0
Dump full memory maps around failing Windows reattach code.

This morning's results from buildfarm member dory make it pretty
clear that something is getting mapped into the just-freed space,
but not what that something is.  Replace my minimalistic probes
with a full dump of the process address space and module space,
based on Noah's work at
<20170403065106.GA2624300%40tornado.leadboat.com>

This is all (probably) to get reverted once we have fixed the
problem, but for now we need information.

Discussion: https://postgr.es/m/25495.1524517820@sss.pgh.pa.us

Files

PathChange+/−
src/backend/Makefile modified +1 −1
src/backend/port/win32_shmem.c modified +89 −45
src/makefiles/Makefile.win32 modified +2 −0
src/tools/msvc/Mkvcbuild.pm modified +2 −0

Discussion