MantisBT - Zandronum
View Issue Details
0001305Zandronum[All Projects] Bugpublic2013-03-24 17:082024-03-19 05:25
Remodeat 
Dusk 
normalminorrandom
closedno change required 
LinuxGentoo Linuxx86_64 3.7.10
1.0 
 
0001305: "Address not mapped to object (signal 11)" in Scythe2.wad
This crash started to occur for me around MAP17, basically what happens is whenever I quicksave, there is a good chance that when I load it, Zandronum will crash with "Address not mapped to object (signal 11)"
1. Warp to a later level (or level with lots of monsters)
2. Quicksave
3. Quickload
4. Crash
It seems to me that the chance this crash occurs increases when Revenant projectiles are tracking me, but I am unsure if this has any effect as to why crashing occurs at all. I have loaded a flawed save game in the windows version and no crash occured. With this being said, I am able to work around the crash by loading it in the windows version, moving to a different location, and then saving again. Running the windows version in wine is a bit more problematic however and using the Linux version is preferred.

Attached below is the output of the console at the time of the crash and zandronum-crash.log
No tags attached.
log zandronumoutput.log (704) 2013-03-24 17:09
/tracker/file_download.php?file_id=951&type=bug
zip crashSave.zds.zip (198,520) 2013-03-24 18:55
/tracker/file_download.php?file_id=952&type=bug
Issue History
2013-03-24 17:08RemodeatNew Issue
2013-03-24 17:09RemodeatFile Added: zandronumoutput.log
2013-03-24 18:55DuskFile Added: crashSave.zds.zip
2013-03-24 18:56DuskNote Added: 0006170
2013-03-24 18:56DuskAssigned To => Dusk
2013-03-24 18:56DuskStatusnew => confirmed
2024-03-19 05:25Ru5tK1ngNote Added: 0023426
2024-03-19 05:25Ru5tK1ngStatusconfirmed => closed
2024-03-19 05:25Ru5tK1ngResolutionopen => no change required

Notes
(0006170)
Dusk   
2013-03-24 18:56   
Kind of difficult to grab a back trace here... attached a save game which crashes Zandronum.

I'll try see if I can pinpoint the source of trouble.
(0023426)
Ru5tK1ng   
2024-03-19 05:25   
If you are still having this issue with zandronum 3.1 or the 3.2 beta, please reopen this ticket.