Re: pg_upgrade segfault (was: pg_migrator segfault)

[hernan gonzalez <hgonzalez@xxxxxxxxx>]

2010/11/2 hernan gonzalez <hgonzalez@xxxxxxxxx>

2010/11/2 Grzegorz JaÅkiewiczÂ<gryzman@xxxxxxxxx>

try gdb --args ./pg_upgrade -d /var/pgsql-8_4_3/data/ -D

/var/pgsql-9_0_1/data/ -b /var/pgsql-8_4_3/bin/ -B
/var/pgsql-9_0_1/bin/ --check -P 5433 -v -g -G debug

and when it fails, type in 'bt' and paste it here please.

--
GJ

I read somewhere that it can happen that a programs segfaults because some allocation problem, which doesnt happen inside gbd (because there some more memory is allocated, or whatever).

Running gbd with the core generated by the segfault, it outputs this:

Program terminated with signal 11, Segmentation fault.

#0 Â0xb7df84ed in _int_realloc () from /lib/libc.so.6

Missing separate debuginfos, use: debuginfo-install glibc-2.11.1-4.i686

(gdb) bt

#0 Â0xb7df84ed in _int_realloc () from /lib/libc.so.6

#1 Â0xb7df88a0 in realloc () from /lib/libc.so.6

#2 Â0xb7db2a5e in __add_to_environ () from /lib/libc.so.6

#3 Â0xb7db27b7 in putenv () from /lib/libc.so.6

#4 Â0x0804aa11 in putenv2 ()

#5 Â0x0804af93 in get_control_data ()

#6 Â0x08049801 in check_cluster_compatibility ()

#7 Â0x0804eb88 in main ()

HernÃn J. GonzÃlez