On Fedora Core 4 test 1, bochs 2.2.pre2 (also happens
with Fedora Core 3, bochs 2.1.1), setting
display_library to "sdl" results in startup failure.
Console output from bochs-dlx:
$ bochs-dlx
DLX Linux Demo, for Bochs x86 Emulator
Checking for bochs binary...ok
Checking for DLX linux directory...ok
Checking for /usr/bin/gzip...ok
Checking for /home/scop/.bochsdlx directory...ok
Entering /home/scop/.bochsdlx
Running bochs
========================================================================
Bochs x86 Emulator 2.2.pre2
Build from CVS snapshot on March 25, 2005
========================================================================
00000000000i[ ] LTDL_LIBRARY_PATH not set. using
compile time default '/usr/lib/bochs/plugins'
00000000000i[ ] BXSHARE not set. using compile time
default '/usr/share/bochs'
00000000000i[ ] reading configuration from bochsrc.txt
00000000000i[ ] lt_dlhandle is 0x8f0d2c0
00000000000i[PLGIN] loaded plugin libbx_sdl.la
00000000000i[ ] installing sdl module as the Bochs GUI
00000000000i[ ] using log file bochsout.txt
========================================================================
Event type: PANIC
Device: [KMAP ]
Message: line 38: unknown host key name 'XK_0'
A PANIC has occurred. Do you want to:
cont - continue execution
alwayscont - continue execution, and don't ask again.
This affects only PANIC events from
device [KMAP ]
die - stop execution now
abort - dump core
Choose one of the actions above: [die] abort
User chose to dump core...
/usr/bin/bochs-dlx: line 108: 8500 Aborted
(core dumped) $BOCHS -q
Backtrace from the resulting core file attached.
Backtrace from SDL GUI startup failure
Logged In: YES
user_id=376477
You have keyboard mapping for the x gui enabled, but sdl needs a
different keymap. It should work when you disable keyboard mapping.
Logged In: YES
user_id=32457
Yep, that seems to work, thanks.
Would it be possible to give a better error message about
what's the problem in this case? For example, if I remeber
correctly, using the wx conflig interface with a non-wx
display library gives a clear error message about what's
wrong with the configuration, something like that would be
useful.
Logged In: YES
user_id=376477
The keyboard mapping feature is independant from the guis and I don't
want to add gui specific stuff there. This panic can also happen when
you try to write your own keymap table and there's a typo in it. I intend to
add "(wrong keymap ?)" to the existing message and add some
information about keymap problems in the docs.
Logged In: YES
user_id=376477
I have improved the panic message and added some information about
panic messages in the user documentation.