Re: [HACKERS] Broken PostgreSQL (latest CVS)

>
> Hi hackers.
>
> I grabbed the latest CVS from this morning and did a clean build
> and initdb.
>
> Things look a little broken as I get a SIGSEGV when trying to
> create a table.

    I  noticed  them  too (but I thought it was a flaw since they
    where gone (up to now) after a 'make install' and  'initdb').

>
> Any idea what went wrong?
>
> Keith.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0xe016e6b4 in _wordcopy_fwd_aligned ()
> (gdb) bt
> #0  0xe016e6b4 in _wordcopy_fwd_aligned ()
> #1  0xe011d62c in memmove ()
> #2  0x26ad0 in DataFill (data=0x1af964 "", tupleDesc=0x4, value=0xefffce3c,
>     nulls=0xefffce40 "", infomask=0xefffcbc6, bit=0x1af958 "\003")
>     at heaptuple.c:208
> #3  0x27abc in index_formtuple (tupleDescriptor=0x15b710, value=0xefffce3c,
>     null=0xefffce40 "") at indextuple.c:78

    Looks like the tuple desctiptor given to index_formtuple() is
    corrupted  somewhere  before  the  call   to   memmove()   in
    DataFill() line 208.

    I  think  it  must  have  happened  inside  of  DataFill() or
    something DataFill() called, because at the time of  failure,
    the  on-stack  variable  tupleDescriptor of index_formtuple()
    looks still good - so I assume index_formtuple()  handed  the
    correct  value  to  DataFill()  at  line  78  and it has been
    corrupted after.

    BTW: I love gdb.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#======================================== jwieck@debis.com (Jan Wieck) #