| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | David Schnur <dnschnur(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Repeatable crash in pg_dump (with -d2 info) |
| Date: | 2011-11-29 02:48:42 |
| Message-ID: | 4ED4480A.6090306@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2011-11-29 04:51:07 | Re: Database is in recovery mode. |
| Previous Message | Craig Ringer | 2011-11-29 02:42:22 | Re: Database is in recovery mode. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marco Bernasocchi | 2011-11-29 14:29:44 | Re: libpq in android |
| Previous Message | Craig Ringer | 2011-11-29 02:33:17 | Re: BUG #6308: Problem w. encoding in client |