Searched refs:segfault (Results 1 – 6 of 6) sorted by relevance
11 static void segfault(int sig) in segfault() function89 sa.sa_handler = segfault; in os_get_top_address()
477 goto segfault; in sys_sigreturn()482 goto segfault; in sys_sigreturn()488 segfault: in sys_sigreturn()578 goto segfault; in sys_rt_sigreturn()583 goto segfault; in sys_rt_sigreturn()589 segfault: in sys_rt_sigreturn()
291 will not run. They will immediately segfault. See ``UML on 2G/2G452 not run. They will immediately segfault. See ``UML on 2G/2G hosts''556 will immediately segfault.3169 thread's stack. I had been seeing the idle thread segfault for no3176 However, the more immediate problem is that second segfault and I'm3396 stick a trap on the segfault handler which will stop if it sees any4156 If the panic was 'segfault in signals', then follow the instructions4194 If you get a segfault, do it again. It always works the second time.
713 occur, but a nice message is better than a kernel segfault.
1032 programs will just segfault, citing addresses of the form
402 bit 1 enables fixups, and bit 2 sends a segfault.