Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id E704C19427CD for ; Mon, 28 Nov 2011 22:49:03 -0400 (AST) Received: from mail-vw0-f46.google.com ([209.85.212.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RVDkl-0000kP-K0 for pgsql-admin@postgresql.org; Tue, 29 Nov 2011 02:49:04 +0000 Received: by vbbfc26 with SMTP id fc26so4376168vbb.19 for ; Mon, 28 Nov 2011 18:48:50 -0800 (PST) Received: by 10.52.35.242 with SMTP id l18mr24501493vdj.39.1322534930630; Mon, 28 Nov 2011 18:48:50 -0800 (PST) Received: from ayaki.localdomain (124-169-45-65.dyn.iinet.net.au. [124.169.45.65]) by mx.google.com with ESMTPS id f11sm48532725vdj.15.2011.11.28.18.48.45 (version=SSLv3 cipher=OTHER); Mon, 28 Nov 2011 18:48:47 -0800 (PST) Message-ID: <4ED4480A.6090306@ringerc.id.au> Date: Tue, 29 Nov 2011 10:48:42 +0800 From: Craig Ringer User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: David Schnur CC: Tom Lane , pgsql-admin@postgresql.org Subject: Re: Repeatable crash in pg_dump (with -d2 info) References: <28131.1322067903@sss.pgh.pa.us> <346.1322071656@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201111/137 X-Sequence-Number: 38731 On 11/29/2011 06:20 AM, David Schnur wrote: > I probably can't get a stack trace Getting a usable stack trace on Windows isn't actually too hard. See: http://wiki.postgresql.org/wiki/Getting_a_stack_trace_of_a_running_PostgreSQL_backend_on_Windows That's focused on debugging the `postgres.exe' backend, but all the setup applies just as well to pg_dump. You then start pg_dump via windbg.exe or Visual Studio Express and, when it crashes, follow the instructions given in the wiki to produce the backtrace. -- Craig Ringer