[http://sourceforge.net/p/ufoai/bugs/2097 Item 2097] imported from sourceforge.net tracker on 2013-01-28 19:18:54

The game (r24291) was loading map +farm when it crashed. There was a flood of "recursive shutdown" messages then a segfault first few lines of backtrace here, more as attachment:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1223878976 (LWP 7123)]
0xb7949a59 in fcntl () from /lib/tls/i686/cmov/libc.so.6
(gdb) bt full
#0 0xb7949a59 in fcntl () from /lib/tls/i686/cmov/libc.so.6
No symbol table info available.
#1 0x0817c057 in Sys_Error (
error=0x81b55d0 "Mem_Free: bad memory header bottom sentinel [buffer underflow]\nfree: %s:#%i") at src/ports/unix/unix_main.c:85
argptr = 0x0
string = &#039;\0&#039; <repeats 1023 times>
#2 0x08137779 in _Mem_CheckSentinels (ptr=0x195eee34,
fileName=0x81b5572 "src/common/mem.c", fileLine=733)
at src/common/mem.c:183
mem = (memBlock_t *) 0x195eee08


Sitll: AthlonXP2000+ (1667Mhz), 1G ram, Linux, Debian Etch

-geever
===== Comments Ported from Sourceforge =====

====== geever (2009-04-29 20:28:38) ======

backtrace
====== geever (2009-05-01 08:41:23) ======

In r24303 the segfault disappeared. But the buffer overflow still exist:

Connecting to localhost...
load material file: &#039;materials/farm.mat&#039;
Error: Mem_Free: bad memory header top sentinel [buffer underflow]
free: src/client/renderer/r_model_brush.c:#904

Program exited with code 01.

-geever
====== aduke1 (2009-05-01 19:47:10) ======

I can confirm the problem on a similar machine, but with Win$ XP SP3.

Also see forums: http://ufoai.ninex.info/forum/index.php?topic=3534.0

I&#039;ve been able to nail it down to rev 24257.
It doesn&#039;t happen with all maps. Only those that have less than 8 levels eg fighter_crash and excavation.
====== tlh2000 (2009-05-02 05:38:26) ======

should be fixed in current trunk
====== aduke1 (2009-05-02 21:31:01) ======

rev 24310 loads fighter_crash and excavation maps nicely again. Thx, tlh2000 :)

geever ?
====== sf-robot (2009-05-17 02:20:22) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).