BUG #1206: sig fault 12 and core dumps using conflux

The following bug has been logged online:

Bug reference: 1206
Logged by: Ertan Kucukoglu

Email address: ertank(at)softhome(dot)net

PostgreSQL version: 7.4

Operating system: FreeBSD 5.2-CURRENT (port build)

Description: sig fault 12 and core dumps using conflux

Details:

I just have below lines in my log:
Aug 5 11:40:52 furby kernel: pid 75103 (postgres), uid 70: exited on
> signal 12 (core dumped)
> Aug 5 11:40:52 furby postgres[75104]: [5-1] WARNING: terminating
> connection because of crash of another server process
> Aug 5 11:40:52 furby postgres[75104]: [5-2] DETAIL: The postmaster has
> commanded this server process to roll back the current transaction and
> exit, because another server
> Aug 5 11:40:52 furby postgres[75104]: [5-3] process exited abnormally
> and possibly corrupted shared memory.
> Aug 5 11:40:52 furby postgres[75104]: [5-4] HINT: In a moment you should
> be able to reconnect to the database and repeat your command.
>
> [snipped]
>
> Aug 5 11:40:53 furby postgres[75115]: [5-1] WARNING: terminating
> connection because of crash of another server process
> Aug 5 11:40:53 furby postgres[75115]: [5-2] DETAIL: The postmaster has
> commanded this server process to roll back the current transaction and
> exit, because another server
> Aug 5 11:40:53 furby postgres[75115]: [5-3] process exited abnormally
> and possibly corrupted shared memory.
> Aug 5 11:40:53 furby postgres[75115]: [5-4] HINT: In a moment you should
> be able to reconnect to the database and repeat your command.
> Aug 5 11:43:14 furby kernel: pid 75133 (postgres), uid 70: exited on
> signal 12 (core dumped)
> Aug 5 11:43:14 furby postgres[75132]: [8-1] WARNING: terminating
> connection because of crash of another server process
> Aug 5 11:43:14 furby postgres[75132]: [8-2] DETAIL: The postmaster has
> commanded this server process to roll back the current transaction and
> exit, because another server
> Aug 5 11:43:14 furby postgres[75132]: [8-3] process exited abnormally
> and possibly corrupted shared memory.
> Aug 5 11:43:14 furby postgres[75132]: [8-4] HINT: In a moment you should
> be able to reconnect to the database and repeat your command.