On Sat, 25 Jun 2005 15:06:05 +0200 Moritz Muehlenhoff wrote:

> Can you run prboom with catchsegv please or send a backtrace from gdb?
> (Preferably with enabled debug symbols)

I tried hard to do so, but still no luck...  :-(
What I did:
___________
First test:

I used catchsegv on sarge prboom, but I got no special output
whatsoever, apart from the one I'm used to get *without* catchsegv.
So it seems like prboom does not actually segfault: I'm puzzled...

$ catchsegv prboom

prboom v2.2.6 (http://prboom.sourceforge.net/)
Z_Init : Allocated 8064Kb zone memory
 found /usr/share/games/doom/doom2.wad
IWAD found: /usr/share/games/doom/doom2.wad
PrBoom (built Mar 13 2005), playing: DOOM 2: Hell on Earth
PrBoom is released under the GNU General Public license v2.0.
You are welcome to redistribute it under certain conditions.
It comes with ABSOLUTELY NO WARRANTY. See the file COPYING for details.
M_LoadDefaults: Load system defaults.
 default file: /home/frx/.prboom/prboom.cfg
I_SetRes: Using resolution 640x400
V_Init: allocate screens.
 found /usr/share/games/doom/prboom.wad
D_InitNetGame: Checking for network game.
W_Init: Init WADfiles.
 adding /usr/share/games/doom/doom2.wad
 adding /usr/share/games/doom/prboom.wad

M_Init: Init miscellaneous info.
R_Init: Init DOOM refresh daemon - 
R_LoadTrigTables: Endianness...ok.
R_InitData: Textures Flats Sprites 
R_Init: R_InitPlanes R_InitLightTables R_InitSkyMap
R_InitTranslationsTables 
P_Init: Init Playloop state.
I_Init: Setting up machine state.
I_InitSound:  configured audio device with 1024 samples/slice
I_InitSound: sound module ready
S_Init: Setting up sound.
S_Init: default sfx volume 14
HU_Init: Setting up heads up display.
I_InitGraphics: 640x400
I_UpdateVideoMode: 640x400 (fullscreen)
I_UpdateVideoMode: 0xe0000000, SDL buffer, direct access
I_InitJoystick : invalid joystick 1
ST_Init: Init status bar.
open /dev/sequencer: Device or resource busy
Using normal BSP nodes!
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
write /dev/sequencer: Bad file descriptor
I_SignalHandler: Exiting on signal: signal 11
I_ShutdownMusic: removing /tmp/prboom-music-XoNlJp
I_ShutdownSound:
 
____________
Second test:

I ran sarge prboom inside gdb and was astonished.
Inside gdb, prboom freezes after some seconds of playing and there seems
to be no way to regain control of the X11 session.
Mouse and keyboard are ignored, apart from special key combinations. If
I switch to a virtual terminal (say tty1: CTRL+ALT+F1), kill gdb, and
switch back to my X11 display, then all I see is a frozen gnome2 desktop
still at low resolution (the one used by prboom: 640x400): mouse is
ignored, while keyboard is not and can be used to type commands inside
the focused xterm.
The only way out I could find was killing the X server with
CTRL+ALT+BACKSPACE...

____________
Other tests:

I recompiled prboom with debug symbols and no stripping.
I reran the above described tests.
Same results!


OK, what did I fail to understand?

-- 
    :-(   This Universe is buggy! Where's the Creator's BTS?   ;-)
......................................................................
  Francesco Poli                             GnuPG Key ID = DD6DFCF4
 Key fingerprint = C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4

Attachment: pgpeSFflK3M5v.pgp
Description: PGP signature

Reply via email to