0ct0pu5/ladybird
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
ladybird/Base/usr/share/man/man1/crash.md
Andreas Kling e56daf547c Kernel: Disallow syscalls from writeable memory 
Processes will now crash with SIGSEGV if they attempt making a syscall
from PROT_WRITE memory.

This neat idea comes from OpenBSD. :^)
2019-11-29 16:30:05 +01:00

1 KiB
Raw Blame History

Name

crash - intentionally perform an illegal operation

Synopsis

$ crash [options]

Description

This program is used to test how the Serenity kernel handles userspace crashes, and can be used to simulate many different kinds of crashes.

Options

  • -s: Perform a segmentation violation by dereferencing an invalid pointer.
  • -d: Perform a division by zero.
  • -i: Execute an illegal CPU instruction.
  • -a: Call abort().
  • -m: Read a pointer from uninitialized memory, then read from it.
  • -f: Read a pointer from memory freed using free(), then read from it.
  • -M: Read a pointer from uninitialized memory, then write to it.
  • -F: Read a pointer from memory freed using free(), then write to it.
  • -r: Write to read-only memory.
  • -T: Make a syscall while using an invalid stack pointer.
  • -t: Trigger a page fault while using an invalid stack pointer.
  • -S: Make a syscall from writeable memory.

Examples

$ crash -F
Shell: crash(33) exitied due to signal "Segmentation violation"