Re: initdb segfaulting.

On Wed, 11 Dec 2002, Tom Lane wrote:

> Rudy Lippan <rlippan(at)remotelinux(dot)com> writes:
> > postgres(at)war PGDATA $ date
> > Sat Dec 14 02:12:00 Local time zone must be set--see zic manual page 2002
>
> You've got a moderately broken platform there, IMHO. Everyone else in
> the world defaults to GMT behavior if no recognizable timezone is set.

I don't know about that. I just screwed up the time zone when setting up
the system, and keep forgetting to fix it -- it acts as if it is set to
GMT; however, the timezone name indicates that you have not configured the
timezone on your system.

I submitted the bug because I thought it might be indicative of a larger
problem. IMO segfault == bug. And there is that tendency for bugs to live
together.

> But if you can provide a stack trace showing just where the backend is
> choking, we could try to defend against this.
>

#0 0x0811bac8 in AtEOXact_Buffers (isCommit=1 '\001') at bufmgr.c:914
914 if (PrivateRefCount[i] != 0)
(gdb) bt
#0 0x0811bac8 in AtEOXact_Buffers (isCommit=1 '\001') at bufmgr.c:914
#1 0x08087980 in CommitTransaction () at xact.c:1018
#2 0x08087c52 in CommitTransactionCommand (forceCommit=1) at xact.c:1304
#3 0x0808cf04 in do_end () at bootparse.y:66
#4 0x0808d231 in Int_yyparse () at bootparse.y:143
#5 0x0808ef68 in BootstrapMain (argc=7, argv=0x823dbe4) at
bootstrap.c:445
#6 0x080e94a1 in main (argc=8, argv=0xbffffcd4) at main.c:218
#7 0x401c2671 in __libc_start_main () from /lib/libc.so.6
(gdb) print i
$1 = 59320
(gdb) print NBuffers
$2 = 762602867

=================

Update:

Just thought to play with this a bit more and:

TZ="AAAAAAAAAAAAAAAAAAAAAAAAAA" ../pgsql7.3/bin/initdb <-- segfault
TZ="AAAAAAAAAAAAAAAAAAAAAAAAA" ../pgsql7.3/bin/initdb <-- initdb failed
TZ="AAAAAAAAAAAAAAAAAAAAAAAA" ../pgsql7.3/bin/initdb <-- works.

Looks like a simple buffer overrun.

-r