Re: pg_dump 8.0.3 failing against PostgreSQL 7.3.2

Tom Lane wrote:
> Jochem van Dieten <jochemd(at)oli(dot)tudelft(dot)nl> writes:
>>
>> (gdb) break elog
>> Breakpoint 1 at 0x16d8f8
>> (gdb) bt
>> #0 0x403ca553 in ?? () from /usr/lib/libc.so.28.5
>> #1 0x10e604 in mdread ()
>> #2 0x10f31f in smgrread ()
>
> You forgot to "continue" until the breakpoint is reached --- this trace
> just indicates where the backend happened to be when you stopped it by
> attaching.

That's different from backtracing a core dump :) This better?

Attaching to process 22733
0x403827df in ?? ()
(gdb) symbol-file postmaster
Reading symbols from postmaster...done.
(gdb) break elog
Breakpoint 1 at 0x16d8f8
(gdb) continue
Continuing.

Breakpoint 1, 0x16d8f8 in elog ()
(gdb) bt
#0 0x16d8f8 in elog ()
#1 0x110abb in pg_exec_query_string ()
#2 0x112a91 in PostgresMain ()
#3 0xf4eae in DoBackend ()
#4 0xf463d in BackendStartup ()
#5 0xf3040 in ServerLoop ()
#6 0xf2502 in PostmasterMain ()
#7 0xc9926 in main ()
(gdb) detach

Jochem