On Mon, May 10, 2004 at 11:59:40AM -0400, Andrew Sullivan wrote:
>
> On the weekend, we ran a set of tests on the offending system to see
> if we could re-create it. We set up the triggering conditions just
> as they'd been when it happened, and alas, no segfault. So although
> this was pretty much regularly reproducible when it actually
> happened, it's now a note to the Journal of Irreproducible Results.
> I hate when that happens.
I hate it even more when the symptom comes back inexplicably. We had
it again. For the record, here's what gdb says (there are some
high-bit characters in here; dunno how they'll come though in mail):
(gdb) bt
#0 0xd01d7778 in memmove () from /usr/lib/libc.a(shr.o)
#1 0xd0326e1c in getaddrinfo2 () from /usr/lib/libc.a(shr.o)
#2 0xd0327b6c in getaddrinfo () from /usr/lib/libc.a(shr.o)
#3 0x10058668 in WriteControlFile () at xlog.c:2121
#4 0x101f8f78 in init_execution_state (src=0x202acd8c "", argOidVect=0x7308710b, nargs=4, rettype=539520040,
haspolyarg=-104'\230') at functions.c:121
#5 0x101f9304 in init_sql_fcache (finfo=0xdeadbeef) at functions.c:250
#6 0x101fa57c in set_tz (tz=0x7308710b <Address 0x7308710b out of bounds>) at variable.c:261
#7 0x101fa9a4 in assign_timezone (value=0x202ad398 "", doit=-1 '�', interactive=-8 '�') at variable.c:584
#8 0x1000466c in PostgresMain (argc=1, argv=0x2002cf38, username=0x1 "") at postgres.c:2560
#9 0x100040b0 in PostgresMain (argc=537240896, argv=0xdeadbeef, username=0xdeadbeef <Address 0xdeadbeef out of
bounds>)at postgres.c:2307
#10 0x10002530 in exec_parse_message (query_string=0x20000a24 "", stmt_name=0x5 "", paramTypes=0x0, numParams=0) at
postgres.c:1216
#11 0x10001f84 in exec_simple_query ( query_string=0x2005a540 '�' <repeats 40 times>) at postgres.c:980
#12 0x100005f0 in main (argc=1, argv=0xdeadbeef) at main.c:228
--
Andrew Sullivan | ajs@crankycanuck.ca
I remember when computers were frustrating because they *did* exactly what
you told them to. That actually seems sort of quaint now. --J.D. Baldwin
