Re: VACUUM ANALYZE

Hmm, unfortunate (was hoping that only the bottom of the trace
was only addresses).  Can you turn on --enable-debug (from configure),
recompile, and see if it crashes then and what the trace is from that?
I think that'd be sufficient in general to get routine names (if I'm
wrong, I'm sure Tom will correct me...)

On Fri, 20 Jul 2001, Ben-Nes Michael wrote:

> Gr8, here it is :)
>
> GNU gdb 5.0
> Copyright 2000 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for details.
> This GDB was configured as "i386-redhat-linux".
> Core was generated by `postgres: admin canada-centre.co.il_album [local]
> VACUUM    '.
> Program terminated with signal 11, Segmentation fault.
> #0  0x4014d8e0 in ?? ()
> (gdb)
> (gdb)
> (gdb)
> (gdb) bt
> #0  0x4014d8e0 in ?? ()
> #1  0x8123a52 in ?? ()
> #2  0x8123a9f in ?? ()
> #3  0x8123caa in ?? ()
> #4  0x8135f3a in ?? ()
> #5  0x80ae162 in ?? ()
> #6  0x80ade39 in ?? ()
> #7  0x80aa4a6 in ?? ()
> #8  0x80aa415 in ?? ()
> #9  0x80fd36f in ?? ()
> #10 0x80fb295 in ?? ()
> #11 0x80fc2ee in ?? ()
> #12 0x80e7410 in ?? ()
> #13 0x80e700f in ?? ()
> #14 0x80e6285 in ?? ()
> #15 0x80e5cd0 in ?? ()
> #16 0x80c7521 in ?? ()
> #17 0x400eaa2c in ?? ()