VOGONS


First post, by TeaRex

User metadata
Rank Member
Rank
Member

Is this a known problem? I'll add more info if it isn't but I don't want to duplicate work that is already being done by others. It's an (almost) unmodified CVS (only thing non-standard in my CVS are the VGA font bitmaps, which IMHO would be very unlikely to cause this.) Build is entirely standard, ./autogen.sh, ./configure without options, make, make install

DOSBox version 0.73
Copyright 2002-2009 DOSBox Team, published under GNU GPL.
---
CONFIG:Loading primary settings from config file dosbox.conf
MIDI:Opened device:none
Using joystick MOSIC SPEED-LINK Competition Pro with 2 axes, 4 buttons and 0 hat(s)
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 142 (MIT-SHM)
Minor opcode of failed request: 3 (X_ShmPutImage)
Value in failed request: 0x245
Serial number of failed request: 105
Current serial number in output stream: 106
Segmentation fault (core dumped)

tearex

Reply 1 of 6, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

sdl version?

Does it happen with the 0.73 release sources as well?

Reply 2 of 6, by TeaRex

User metadata
Rank Member
Rank
Member

The libsdl1.2-dev package is version 1.2.13-4ubuntu4; sdl-config --version just gives 1.2.13

Yes, the bug happens with the 0.73 release sources as well.

It happens only with at least gcc/g++ -O1 though; at gcc -O0 it works.

Also it happens only if fullscreen=true is in the conf file, not if you switch to fullscreen manually after DOSBox is already running.

I'm at a loss on how to run gdb on this. I mean I can run it, but then the screen just goes black and I have to "killall -9 dosbox" from a virtual console; after that of course I can't do any "bt full", "disass" or anything else in gdb any more because the memory is gone. The only info that I can give you is the error location:

0x0000000000529132 in RENDER_EndUpdate () at render.cpp:224
render.frameskip.hadSkip[render.frameskip.index] = 0;

I should add: this is the 64-bit Ubuntu. I'll attach my whole conf file as well. Please tell me what else you would need (valgrind, how to run gdb on this and what to do in it; etc.)

tearex

Reply 3 of 6, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

the location can technically cause a segfault. So the location might be a valid one.

Try this
open a xterminal and type echo $DISPLAY
Note down the answer
switch to a terminal (with ctrl-alt-f1 )
login
export DISPLAY= that number your wrote down
start gdb dosbox
run

not sure if it will crash at the same location though. At my place this seems to trigger crash in SDL_Init. so probably not the same thing as you.

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

Reply 4 of 6, by TeaRex

User metadata
Rank Member
Rank
Member

It did crash at the same location.

gdb output attached.

Note: this is the 0.73 release.

tearex

Reply 5 of 6, by TeaRex

User metadata
Rank Member
Rank
Member

Just FYI, this bug has disappeared. I didn't look closely at the newest changes in CVS, or in the Ubuntu Karmic packages, but it seems to be gone now. Thanks a lot. to whoever is responsible.

tearex

Reply 6 of 6, by wd

User metadata
Rank DOSBox Author
Rank
DOSBox Author

Could you please see if yesterday's (or friday's whatever) cvs sources exhibit the problem?