Thread: pgsql: Dump full memory maps around failing Windows reattach code.
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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/6ba0cc4bd3a6d738eddf7e8aa2ef7b46cdd9ce8f Modified Files -------------- src/backend/Makefile | 2 +- src/backend/port/win32_shmem.c | 134 +++++++++++++++++++++++++++-------------- src/makefiles/Makefile.win32 | 2 + src/tools/msvc/Mkvcbuild.pm | 2 + 4 files changed, 94 insertions(+), 46 deletions(-)