Messages in this thread |  | | | From | yodaiken@chelm ... | | Date | Thu, 13 Aug 1998 05:47:53 -0600 | | Subject | Re: kill -9 <pid of X> |
| |
On Thu, Aug 13, 1998 at 02:12:45PM +0200, Olaf Titz wrote: > > Why is your X server in a tight loop with signals blocked? > > Bacause of a bug in it? ;-) > > > For example, it _never_ makes any sense to block SIGSEGV. For all I know, > > XFree86 and svgalib apps _must_ block/catch SIGSEGV precisely because > that signal can occur at any time and exiting then leaves the hardware > in an undefined state. Just like with SIGTERM. The fact that SIGSEGV
So the isn't the correct approach to _catch_ SIGSEGV and to do a safe exit or for X to run as the child of a process that knows how to safe exit when X die? In fact, wouldn't is be reasonable to have a collection of X parents that would save video state, fork/exec X and take care of cleanup? These would be small, easy to debug programs, as far as I can tell.
--------------------------------- Victor Yodaiken Department of Computer Science New Mexico Institute of Mining and Technology Socorro NM 87801 Homepage http://www.cs.nmt.edu/~yodaiken PowerPC Linux page http://linuxppc.cs.nmt.edu Real-Time Page http://rtlinux.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html
|  |