Re: Buildfarm member gypsy_moth seems not to like alignment patch - Mailing list pgsql-hackers

From Jorgen Austvik - Sun Norway
Subject Re: Buildfarm member gypsy_moth seems not to like alignment patch
Date
Msg-id 47C6BAE1.7000806@sun.com
Whole thread Raw
In response to Buildfarm member gypsy_moth seems not to like alignment patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> Tom Lane wrote:
>> This is unfortunate and surprising, since that patch was intended to
>> prevent compilers from making unsafe alignment assumptions, but it sure
>> looks like this compiler has instead added a new one.  Could you poke
>> into it --- at least get a stack trace from the core dump?

Forgot some information about local variables:

(dbx) dump
toasttupDesc = 0xcf9538
chunk_size = 1996
t_values = ARRAY
toast_pointer = RECORD
chunk_seq = 1
rel = 0xcd8ff8
toastidx = 0xcf9858
toasttup = 0x8
toastrel = 0xcf9748
use_wal = '\001'
result = 0x1
data_p = 0xdbd354 ""
use_fsm = '\001'
data_todo = 2286
mycid = 10U
__func__ = "toast_save_datum"
t_isnull = ARRAY
value = 14406480U
chunk_data = RECORD
(dbx) print toast_pointer
toast_pointer = {
     va_rawsize    = 11963
     va_extsize    = 2286
     va_valueid    = 10953U
     va_toastrelid = 2838U
}
(dbx) print t_values
t_values = (10953U, 0, 4290673827U)
(dbx) print t_isnull
t_isnull = ""
(dbx) print chunk_data
chunk_data = {
     hdr  = {
         vl_len_ = ""
         vl_dat  = ""
     }
     data = ""
}

-J
--

Jørgen Austvik, Software Engineering - QA
Sun Microsystems Database Technology Group

Attachment

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Logging conflicted queries on deadlocks
Next
From: Jorgen Austvik - Sun Norway
Date:
Subject: Re: Buildfarm member gypsy_moth seems not to like alignment patch