VOGONS


First post, by CMDRSweeper

User metadata
Rank Newbie
Rank
Newbie

When I try to run Fragile Allegiance under DOSBox the game seems to run fine for a while, roughly 1-2 minutes before I get a hard CTD to desktop.
This is not an application crash, as the game runs fine under DOSBox 0.73 and 0.74 under Windows, but on my Linux laptop it causes DOSBox to crash.
The crash itself leaves no errors, no traces, even when checking my journalctl -r, the last few lines in the log are:

Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> Using joystick ST LIS3LV02DL Accelerometer with 3 axes, 0 buttons and 0 hat(s)
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> One joystick reported, initializing with 4axis
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> MIDI:Opened device:none
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> ALSA:Can't subscribe to MIDI port (65:0) nor (17:0)
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> MIXER:Got different values from SDL: freq 44100, blocksize 512
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> CONFIG:Loading additional settings from config file /home/sweeper/.dbgl/profiles/7.conf
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> CONFIG:Loading primary settings from config file /home/sweeper/.dosbox/dosbox-0.74.conf
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> ---
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> Copyright 2002-2010 DOSBox Team, published under GNU GPL.
Dec 15 18:35:31 sweeperhe119315 slim[451]: DOSBox stdout> DOSBox version 0.74

There are a couple of other games that have this issue as well, Death Rally and Deadly Games.
Is there a way to put DOSBox in a debug mode so you can know what it was doing when it crashed? I haven't found any such setting except somebody mentioning recompiling DOSBox which is a bit... excessive.

System specs:
HP EliteBook 8540p
OS: Arch Linux
Nvidia properitary driver

Reply 1 of 4, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

Try with current SVN of Dosbox. My guess is that your linux is 64bit and Dosbox is thus by default also in 64bit. Since 0.74 some fixes landed in SVN to make it behave better in 64bit mode.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper

Reply 2 of 4, by CMDRSweeper

User metadata
Rank Newbie
Rank
Newbie

I gave DOSBox 0.74.3935-1 from a SVN Build a go, sadly the same issue persists, and no output to the log 🙁
So there exists no way to make DOSBox more verboose like other programs for Linux in an effort to determine where it breaks?
But yes, my Linux distro is 64 Bit, but I do have the multilib's enabled if it that makes a difference (32 Bit libraries for 32 Bit applications like Steam)

Reply 3 of 4, by Dominus

User metadata
Rank DOSBox Moderator
Rank
DOSBox Moderator

You can built with debug enabled (configure option). And you can build as 32bit...
And you can always run it in gdb which will tell you where it breaks.

Windows 3.1x guide for DOSBox
60 seconds guide to DOSBox
DOSBox SVN snapshot for macOS (10.4-11.x ppc/intel 32/64bit) notarized for gatekeeper