osprey dumped core on 8.2 - Mailing list pgsql-hackers

From Alvaro Herrera
Subject osprey dumped core on 8.2
Date
Msg-id 20070223154308.GA17656@alvh.no-ip.org
Whole thread Raw
Responses Re: osprey dumped core on 8.2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Osprey is a NetBSD running on m68k

http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=osprey&dt=2007-02-22%2023:00:18

It dumped core running VACUUM:

--- 1,5 ---- VACUUM;
! server closed the connection unexpectedly
!     This probably means the server terminated abnormally
!     before or while processing the request.
! connection to server was lost


The stack trace report looks incomplete:

================== stack trace: pgsql.27009/src/test/regress/tmp_check/data/postgres.core ==================
Core was generated by `postgres'.
Program terminated with signal 11, Segmentation fault.
#0  0x001f74d6 in AllocSetAlloc (context=0x307d10, size=16777212) at aset.c:546
546            if (set->blocks != NULL)

It's missing the "bt" part.


I don't understand how can this happen, given that "set" cannot be NULL
at this point.

-- 
Alvaro Herrera                 http://www.amazon.com/gp/registry/CTMLCN8V17R4
"Puedes elegir el color de tu auto -- siempre y cuando sea negro."
(HenryFord)
 


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: SCMS question
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Simple Column reordering