=?ISO-8859-1?Q?Gunthard_St=FCbs?= <stuebs2...@gmx.de> writes:
> I installed v9.1 on linux (older suse distr.) from source code using
> configure --without-readline (in case that it is important).
> performing initdb --locale=de_DE.UTF-8 -D /usr/local/pgsql/data/ everything
> run fine until:
> vacuuming database template1 ... ok
> copying template1 to template0 ... child process exited with exit code 139
> initdb: removing contents of data directory "/usr/local/pgsql/data"
Hmm, that's pretty interesting. Exit code 139 is presumably a SIGSEGV,
but it's surprising that it would get that far and then crash.
Please (1) rebuild with --enable-cassert and --enable-debug configure
options, if you didn't already; (2) set "ulimit -c unlimited" if that's
not the default in your environment; (3) run initdb with the --noclean
option; (4) look into /usr/local/pgsql/data to find the core file left
behind by the crash, and do
$ gdb /usr/local/bin/postgres /path/to/core-file
gdb> bt
gdb> quit
(5) post the output of "bt" here.
BTW, what compiler version are you using exactly, and what compiler options?
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
