On Wed, Feb 06, 2019 at 07:47:19PM -0600, Justin Pryzby wrote:
> FYI, I wasn't yet able to make this work yet.
> (gdb) print *segment_map->header
> Cannot access memory at address 0x7f347e554000
I'm still not able to make this work. Actually this doesn't work even:
(gdb) print *segment_map
Cannot access memory at address 0x4227dcdd0
Thomas thought it's due to coredump_filter, but 0xff doesn't work (actually
0x7f seems to be the max here). Any other ideas? The core is not being
truncated, since this is on a "toy" instance with 128MB buffers.
-rw-r-----. 1 pryzbyj root 279M Feb 7 09:52 coredump
[pryzbyj@telsasoft-db postgresql]$ ~/src/postgresql.bin/bin/pg_ctl -c start -D /var/lib/pgsql/test -o '-c
operator_precedence_warning=on-c maintenance_work_mem=1GB -c max_wal_size=16GB -c full_page_writes=off -c
autovacuum=off-c fsync=off -c port=5678 -c unix_socket_directories=/tmp'
waiting for server to start....2019-02-07 09:25:45.745 EST [30741] LOG:
listeningon IPv6 address "::1", port 5678
2019-02-0709:25:45.745 EST [30741] LOG: listening on IPv4 address "127.0.0.1", port 5678
2019-02-07 09:25:45.746 EST [30741] LOG: listening
onUnix socket "/tmp/.s.PGSQL.5678"
.2019-02-07 09:25:46.798 EST [30741] LOG: redirecting log output to logging collector process
2019-02-07 09:25:46.798 EST [30741] HINT: Future log output will appear in directory "log".
done
server started
[pryzbyj@telsasoft-db postgresql]$ echo 0xff |sudo tee /proc/30741/coredump_filter
Justin
