Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grlI8-0005lt-Sb for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Feb 2019 15:08:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1grlI7-0007Ml-J2 for pgsql-hackers@arkaria.postgresql.org; Thu, 07 Feb 2019 15:08:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grlI7-0007Me-3w for pgsql-hackers@lists.postgresql.org; Thu, 07 Feb 2019 15:08:39 +0000 Received: from mail-it1-x12b.google.com ([2607:f8b0:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1grlI4-0004F3-5O for pgsql-hackers@lists.postgresql.org; Thu, 07 Feb 2019 15:08:37 +0000 Received: by mail-it1-x12b.google.com with SMTP id z20so436532itc.3 for ; Thu, 07 Feb 2019 07:08:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=R5GEVlLemU+esd4R72rjO0B0rZIRNyFJE8o2PDcnV6U=; b=p0oD4p8PEst7H/xFgqdwrf9lCuCbOrtpWYJwxyyo2lZBBqIVwJ8lC4glqkDkaIKDh/ pbKDtEocPsC5eIojuuNsLvIJIQ/8MBD7dpAZdyDxYhmQuxzOeB/L00LE5erIFxuJJTcd ng2Zlcto5CXXMXQghgsaz7jN4OjeMLa80ZVY30EHv6jlhQe4UoSyNjzyTBTyTG/yGWkp H3h3/xd9sYrwD/+c9aWYa+jvTUq7lxHXg3WZTOwwazIhD3EodzqNiKxN1ET/UW5TBCFv Jj6SH+IBEC4MGd6+PztMei/pde+N8p4gn9Vb2+LO+q74RVQxRarfVw8HzF9XRUMtSHMc pHew== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=R5GEVlLemU+esd4R72rjO0B0rZIRNyFJE8o2PDcnV6U=; b=rrQgr9wlZDoDzpkH9ZgySE7rV3N7PgvmQa32tkBnlB6rvBOGC/h9ph12ey9UUey+gB xpcNPSGdQ6kge9SDsttCwy6BB10DNqqLCPSioLX2n5VT7JI/IgNd6y6QfEZBNJSwXN3+ aGN74C6igLLyu8CPp/MmcNI6sE8ni784pUqaKY6MjgXcx0yJCObGTmenTtnvtDXPmU0L QHZap93xKEmRbfmSnwwEeExgDu4PV2pJtAXeuDmo+uqFOxQSvL6iiWAQt1ZPdgy88Ib4 0vr3SkyU+xqZWszs3perobisGr8CNwpEstJsbFHTQKFIAKjgBtptiGT1+paMTcs2maM8 34+A== X-Gm-Message-State: AHQUAuZG0/Kx5uhiTJsQuPqzWh4EmJ7IkYEwOaM2l0Bh2Ig76lLthdq/ 3cJSoTz3XIXmWnMugTxbRILA0WygN18= X-Google-Smtp-Source: AHgI3IbwkOHcNCp9U3OtdlmKq6Nkxkko20rJF1jWyb2yDET5DwsBvH094aiDA7IVYD06i/yaX0ntoQ== X-Received: by 2002:a6b:f102:: with SMTP id e2mr1206693iog.195.1549552115089; Thu, 07 Feb 2019 07:08:35 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id r195sm5456986ita.3.2019.02.07.07.08.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 07 Feb 2019 07:08:33 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id CB917800AB8; Thu, 7 Feb 2019 09:08:32 -0600 (CST) Date: Thu, 7 Feb 2019 09:08:32 -0600 From: Justin Pryzby To: Thomas Munro Cc: pgsql-hackers@lists.postgresql.org Subject: Re: pg11.1: dsa_area could not attach to segment Message-ID: <20190207150832.GL29720@telsasoft.com> References: <20190206062427.GX29720@telsasoft.com> <20190206063548.GZ29720@telsasoft.com> <20190206070819.GA29720@telsasoft.com> <20190206071940.GB29720@telsasoft.com> <20190207014719.GJ29720@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190207014719.GJ29720@telsasoft.com> User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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: listening on IPv6 address "::1", port 5678 2019-02-07 09: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 on Unix 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