NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: xsrc/58133: X server crashes; radeon 5450; modesetting
The following reply was made to PR xsrc/58133; it has been noted by GNATS.
From: Rhialto <rhialto%falu.nl@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: xsrc-manager%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
Rhialto <rhialto%falu.nl@localhost>
Subject: Re: xsrc/58133: X server crashes; radeon 5450; modesetting
Date: Sun, 12 May 2024 22:36:40 +0200
> > Typing "c" for continue in gdb simply continued X without causing the
> > expected crash.
>
> FWIW, i've seen this "feature" multiple times, and i don't
> think it is directly related to this problem. something that
> X is doing (and that other things can do) seems to set it up.
There is a signal handler for SIGSEGV and others set up by OsInit() in
xsrc/external/mit/xorg-server/dist/os/osinit.c, and the handler is
OsSigHandler() in the same file. This looks like it is where the stack
trace in the Xorg.0.log file is generated. There may be a detour via a
function pointer OsSigWrapper but that appears to be NULL. A breakpoint
set on OsSigHandler() doesn't trigger.
I didn't find a gdb command to see the state of signals and their
handlers.
Home |
Main Index |
Thread Index |
Old Index