error : moveCalcTurn: target out of range -2147483648.000000
error : Assert in Warzone: move.c:900 : moveCalcTurn (target < 360.0 && target
>= 0.0), last script event: '30 (CALL_STRUCT_ATTACKED)'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to
build too closely to map-edge"), last script event: 'vtolAttack'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to
build too closely to map-edge"), last script event: 'buildOilDefenseOrRetreat'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to
build too closely to map-edge"), last script event: 'buildOilDefenseOrRetreat'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: '30 (CALL_STRUCT_ATTACKED)'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: 'watchMenu'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: '30 (CALL_STRUCT_ATTACKED)'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: 'watchMenu'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: '30 (CALL_STRUCT_ATTACKED)'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: 'watchMenu'
error : buildStructure: y coord (11584) too near edge (req. distance is 3)
error : Assert in Warzone: structure.c:1745 : buildStructure (!"attempting to build too closely to map-edge"), last script event: 'watchMenu'
Failed to read a valid object file image from memory.
Saved dump file to '/tmp/warzone2100.gdmp'
What is this? What can i do? I think about those "build to close to edge" that AI trying to build near the edge.
yes the build assert is caused by AI trying to build a structure on map edge tiles,though I am not sure if that assert is directly associated with the crash.The first assert is probably the culprit of the crash,seems it tried to access to free'ed droid pointer via move functions.
tasks postponed until the trunk is relatively stable again.
revision 2002 should I recompile with the debug options? I now it will crash again.
I have that .gdmp file too.
It happens when a pack of droids are being attacked by vtols with "Tank Killer". Or at least this units are involved.
Last edited by CRISTIAN on 03 Jul 2007, 15:19, edited 1 time in total.
Yes, without debug info the dump is pretty useless. It seems as if you striped the binary... If that's true, you should know that it will remove the debug info.
DevUrandom wrote:
Yes, without debug info the dump is pretty useless. It seems as if you striped the binary... If that's true, you should know that it will remove the debug info.
I believe non-debug (i.e. release) builds simply don't produce debugging symbols (i.e. they don't use -g). Also looking at the asserts I only see the message warzone spits out, but the assertion itself doen't raise a SIGABRT (that means that assert() wasn't defined, and NDEBUG is..).
Compiling with "CFLAGS='-O0 -g' ./configure" should help.
"First make sure it works good, only then make it look good." -- Giel
Want to tip/donate? bitcoin:1EaqP4ZPMvUffazTxm7stoduhprzeabeFh
error : getBaseObjFromId() failed for id -1
error : Assert in Warzone: objmem.c:745 : getBaseObjFromId (!"couldn't find a BASE_OBJ with ID"), last script event: '<none>'
Failed to read a valid object file image from memory.
Saved dump file to '/tmp/warzone2100.gdmp'
Is this useless? the warzone2100.gdmp file looks the same as before (without debug-enabled).
Last edited by CRISTIAN on 04 Jul 2007, 02:48, edited 1 time in total.
error : getBaseObjFromId() failed for id -1
error : Assert in Warzone: objmem.c:745 : getBaseObjFromId (!"couldn't find a BASE_OBJ with ID"), last script event: '<none>'
Failed to read a valid object file image from memory.
Saved dump file to '/tmp/warzone2100.gdmp'
Is this useless? the warzone2100.gdmp file looks the same as before (without debug-enabled).
this is not the same problem,this one is caused by a missing object when loading a save game,though it can be ignored safely if you are lucky enough.
tasks postponed until the trunk is relatively stable again.
error : getBaseObjFromId() failed for id -1
error : Assert in Warzone: objmem.c:745 : getBaseObjFromId (!"couldn't find a BASE_OBJ with ID"), last script event: '<none>'
Failed to read a valid object file image from memory.
Saved dump file to '/tmp/warzone2100.gdmp'
The cause of this crash is the assertion, which is a "simulated" crash (an abortion to be precise). You could prevent it from occuring by compiling without `--debug-enabled` although this also decreases the debug value of the created binary.
CRISTIAN wrote:
the warzone2100.gdmp file looks the same as before (without debug-enabled).
Could you show us the file? Since unless you're used to debugging with gdb you won't know where to look at (it are small differences).
"First make sure it works good, only then make it look good." -- Giel
Want to tip/donate? bitcoin:1EaqP4ZPMvUffazTxm7stoduhprzeabeFh
error : getBaseObjFromId() failed for id -1
error : Assert in Warzone: objmem.c:745 : getBaseObjFromId (!"couldn't find a BASE_OBJ with ID"), last script event: '<none>'
error : moveCalcTurn: target out of range -2147483648.000000
error : Assert in Warzone: move.c:900 : moveCalcTurn (target < 360.0 && target >= 0.0), last script event: 'everySec'
Failed to read a valid object file image from memory.
Saved dump file to '/tmp/warzone2100.gdmp'
Segmentation fault
Attachments
[The extension has been deactivated and can no longer be displayed.]
Yes, I'm afraid you're right this dump is useless as well. Strange is that GDB doesn't even seem to make an attempt to read symbols from the warzone2100 binary.
"First make sure it works good, only then make it look good." -- Giel
Want to tip/donate? bitcoin:1EaqP4ZPMvUffazTxm7stoduhprzeabeFh
"No symbol table info available." -> Pretty much useless...
It compiled with -gX (X != 0)? And you did not strip the binary? You also did not compile with -fomit-frame-pointer? No idea then...
