VOGONS

Search

Common searches

X-Com Apocalypse causing SIGSEGV

Topic actions

First post, by Marty A

Posted on 
User metadata
Rank Newbie
Rank
Newbie

I've got X-Com Apocalypse (retail) running in DosBox .72 on OpenSuse 11, x86-64. I made a CUE/BIN image of the retail CD so that I can run without it. I find that the game is really choppy when it has to wait for real CD seeks and it runs much smoother without it. It wouldn't run with just the ISO image. I see now that I could have skipped the intro to get around that, but with the CUE/BIN, you can actually play the intro and everything else just fine.

In any case, the game has been working great so far, up until now. I'm pretty late in the game, explored some of the alien dimension, getting to the end of the new technologies, and I just shot down 4 UFOs in a single fight. Two of them are type 10's (which I didn't research yet), and the other two were escort ships. I went on the ground mission in the first type 10 ship, reported back to base for resupply, and then went for one of the escorts (which had a cloaking device which I haven't researched yet). I get through the whole ground mission, recover tons of great stuff, and when it goes to exit the TAC2P program after the mission is over, DosBox catches a SIGSEGV.

I tried replaying the whole ground mission from the beginning, and every time the mission is over, no matter what I do differently, it crashes there.

I'm trying to get some debug info out of DosBox, but the console says nothing. I even ran inside of GDB, but I couldn't get control of my system back without killing it because of the mouse and window focus capture. I logged in through a VNC to kill off the debugger to get control of the system again. The debugger offered me nothing other than this:

[Thread debugging using libthread_db enabled]
[New Thread 0x7fba87f7a740 (LWP 4915)]
DOSBox version 0.72
Copyright 2002-2007 DOSBox Team, published under GNU GPL.
---
[New Thread 0x419c4950 (LWP 4916)]
[Thread 0x419c4950 (LWP 4916) exited]
[New Thread 0x419c4950 (LWP 4917)]
CONFIG:Loading primary settings from config file .dboxfe/X-Com Apocalypse.conf
[New Thread 0x421c5950 (LWP 4918)]
[New Thread 0x429c6950 (LWP 4919)]
ALSA:Can't subscribe to MIDI port (65:0) nor (17:0)
MIDI:Opened device:none

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fba87f7a740 (LWP 4915)]
0x0000000000480a3c in ?? ()

How can I get more information on what happened here? Are there some DosBox switches I can turn on to get more info?

This is my favorite game and I'd really like to be able to complete it. Thanks for the great work on DosBox that got me this far.

Reply 1 of 5, by Qbix

Posted on 
User metadata
Rank DOSBox Author
Rank
DOSBox Author

the only ways to get real information from the crash requires you to recompile.

The "easiest one is by activating our debugger"
./configure --enable-debug

create a new configfile and modify the logfile= line so it points to a file you want to save the log in.
Then play and see if anything happends when it crashes.

I would advice you to start with the CVS source. dosbox.linuxsecured.net/dosboxcvs.tgz
as that one a lot more advanced then 0.72

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 5, by Marty A

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Ok. I'll try to get a debug build going and see what happens. In the meantime, I just narrowed down where the problem might be pretty well. I ran it with the default DosBox configuration and it didn't crash. Then I started changing my current configuration back to the defaults and found that it started working when I changed the render options. I was using the advmame3x scaler with aspect ratio corrections. I changed these to using normal2x with no aspect ratio corrections and it's running fine now.

I will keep my saved game (which has been reproducing the situation reliably) and pursue this with the debug build just so we can squash this problem, but in the meantime I can continue my game. 😀

I'll post my findings back to this thread when I have more info.

Reply 3 of 5, by Marty A

Posted on 
User metadata
Rank Newbie
Rank
Newbie

After the very next battle, after I changed my settings, at the end of the battle, it SIGSEGV'd again. So the change in settings seems irrelevant.

Grabbed the CVS image and built it up with debug enabled as you suggested. Good news and bad news... it doesn't crash anymore!

So I can't reproduce the problem using my own debug build. Hopefully it's because the latest code base has many good improvements. 😀

I'll post again here if it happens again and I can get debug info.

Reply 4 of 5, by DosFreak

Posted on 
User metadata
Rank l33t++
Rank
l33t++

Did you ever try playing the game in normal core? I doubt it would be playable enough for testing in normal core but if you could test it with that and it worked then that would narrow it down.

Then you could look through the changelog from 0.72 to the CVS and look for improvements in dyanmic core and try the CVS from those changes.

Not as easy as using a debug build but nowhere near as painful as just going through the CVS randomly at different dates trying to pinpoint the issue.

How To Ask Questions The Smart Way
Make your games work offline

Reply 5 of 5, by vocals

Posted on 
User metadata
Rank Newbie
Rank
Newbie

Hello

this is no Solution to your Problem, but an Workaround

when close to ending the mission,
save the game. Ideally, save when the last alien is killed, just before you get the TAC2P.

After XCOM crashes as described, restart and load the savegame.

Shortly after loading the TAC2P will be shown, without crashing.

edit:
my guess was wrong
hopefully the workaround still works
it does for me so far

Go to top of page Go to top of page
Back to DOSBox Games/Apps
Close window
Close window