project-navigation
Personal tools

Author Topic: [trunk] saving a game is broken  (Read 2779 times)

Punkiee

  • Guest
[trunk] saving a game is broken
« on: August 30, 2007, 11:17:28 pm »
At least, my copy is and i havent touched the structure of datatypes nor the savegame functionality.

Received signal 6, exiting...
Code: [Select]
(gdb) bt
#0  0xb7f31410 in ?? ()
#1  0xbf9e64e8 in ?? ()
#2  0x00000006 in ?? ()
#3  0x000015ce in ?? ()
#4  0xb7cf3fc0 in raise () from /lib/i686/libc.so.6
#5  0xb7cf5851 in abort () from /lib/i686/libc.so.6
#6  0xb7ced53b in __assert_fail () from /lib/i686/libc.so.6
#7  0x080666be in B_Save (sb=0xbf9e681c, data=0x0) at src/client/cl_basemanagement.c:3060
#8  0x080b8563 in SAV_GameSave (filename=0x13f27614 "slot0", comment=0xbf9e6888 "start",
    error=0xbf9e6884) at src/client/cl_save.c:249
#9  0x080b8aa1 in SAV_GameSave_f () at src/client/cl_save.c:337
#10 0x080d603c in Cmd_ExecuteString (text=0xbf9e6904 "game_save slot0 *mn_slot0")
    at src/qcommon/cmd.c:936
#11 0x080d4e47 in Cbuf_Execute () at src/qcommon/cmd.c:266
#12 0x08090052 in CL_SendCommand () at src/client/cl_main.c:2447
#13 0x080905af in CL_Frame (now=29198, data=0x0) at src/client/cl_main.c:2647
#14 0x080e26d8 in tick_timer (now=29198, data=0x139979a8) at src/qcommon/common.c:952
#15 0x080e2931 in Qcommon_Frame () at src/qcommon/common.c:1039
#16 0x081046cb in main (argc=10, argv=0xbf9e6e84) at src/ports/linux/sys_linux.c:393
(gdb)                                                                                       

src/client/cl_basemanagement.c:3060      
assert(*aircraft->aliencargo[l].alientype);

Last Changed Rev: 11262
Last Changed Date: 2007-08-30 18:44:25 +0200 (Thu, 30 Aug 2007)

Offline Mattn

  • Administrator
  • PHALANX Commander
  • *****
  • Posts: 4831
  • https://github.com/mgerhardy/vengi
    • View Profile
    • Vengi Voxel Tools

Offline Zenerka

  • Sergeant
  • *****
  • Posts: 301
    • View Profile
Re: [trunk] saving a game is broken
« Reply #2 on: September 04, 2007, 11:00:58 am »
This one was just wrongly placed assert, and is fixed.