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

From Tom Lane
Subject Buildfarm member gypsy_moth seems not to like alignment patch
Date
Msg-id 14715.1204160028@sss.pgh.pa.us
Whole thread Raw
Responses Re: Buildfarm member gypsy_moth seems not to like alignment patch
List pgsql-hackers
It looks like gypsy_moth has been failing like this:

creating directory /export/home/tmp/pg-test/build-suncc/HEAD/pgsql.21325/src/test/regress/./tmp_check/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in
/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.21325/src/test/regress/./tmp_check/data/base/1... ok
 
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... Bus Error - core dumped
child process exited with exit code 138
initdb: data directory "/export/home/tmp/pg-test/build-suncc/HEAD/pgsql.21325/src/test/regress/./tmp_check/data" not
removedat user's request
 

since I put in this patch:
http://archives.postgresql.org/pgsql-committers/2008-02/msg00270.php

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?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: Re: OSSP can be used in the windows environment now!
Next
From: Simon Riggs
Date:
Subject: Re: Producer/Consumer Issues in the COPY across network