Skip site navigation (1) Skip section navigation (2)

Buildfarm member gypsy_moth seems not to like alignment patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: gorm(dot)andersen(at)sun(dot)com
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Buildfarm member gypsy_moth seems not to like alignment patch
Date: 2008-02-28 00:53:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: 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 removed at user's request

since I put in this patch:

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

Next:From: Simon RiggsDate: 2008-02-28 01:57:49
Subject: Re: Producer/Consumer Issues in the COPY across network
Previous:From: Hiroshi SaitoDate: 2008-02-28 00:38:00
Subject: Re: OSSP can be used in the windows environment now!

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group