Sergio P.Korlowsky wrote:
> On Saturday 08 September 2001 15:13, you wrote:
>
>>"Sergio P.Korlowsky" <[EMAIL PROTECTED]> writes:
>>
>>
>>[...]
>>
>>
>>>But... I am having a problem to run quake3 or q3demo either one.
>>>First I thought it was a problems related to the GLide drivers... Nop
>>>I was wrong... it IS related to sound!
>>>
>>To isolate, you can try to mv (or chmod for devfs probably) the /dev/dsp
>>file so that sound can't start.
>>
>>
>>[...]
>>
>>
>>>------- sound initialization -------
>>>------------------------------------
>>>Received signal 11, exiting...
>>>[admin@linux admin]$
>>>
>>>BTW... signal 11, is not related to the X server?
>>>
>>Signal 11 means segmentation fault.
>>
>>[gc@obiwan ~] grep -w 11 /usr/include/asm/signal.h
>>#define SIGSEGV 11
>>
>>
>>>maybe is not related to sound after all... (?)
>>>
>>You may try to strace the program.
>>
> -----------------------------------------
> here is the result
>
> Received signal 11, exiting...
> [WIFEXITED(s) && WEXITSTATUS(s) == 0], 0, NULL) = 30539
> rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [CHLD], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
> rt_sigprocmask(SIG_BLOCK, [CHLD], [CHLD], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> --- SIGCHLD (Child exited) ---
> wait4(-1, 0xbffff270, WNOHANG, NULL) = -1 ECHILD (No child processes)
> sigreturn() = ? (mask now [])
> rt_sigaction(SIGINT, {SIG_DFL}, {0x8075660, [], 0x4000000}, 8) = 0
> rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
> rt_sigprocmask(SIG_BLOCK, [CHLD TTOU], [], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> read(255, "exit 0 \n\n", 151) = 9
> rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
> _exit(0) = ?
> [admin@linux admin]$
>
> Any Ideas? is greek to me!
Basically there are probably a few processes running in parallel, and
the faulty one should handle sound, right? Well, the other one handles
the initialization of the game, it is this process that you launch with
the initial command. But, for some unknown reason, the child stops (see
the SIGCHLD signal?), and the father stops shortly afterwards.
In fact, the above data is probably only related to the main process,
not the one which handles sound, so I think it's quite useless. We can
only see that the sound process is dead, but cannot see why. Though, on
the previous message, you wrote that the signal was SIGSEGV, and here,
the main process quits gracefully (exit(0)). That's odd.
Gr�goire
Disclaimer : all the above is written by a student, late at night, so
may be inacurate. :-/
