ladybird/Base/usr/share/man/man1/crash.md
Andreas Kling f41ae755ec Kernel: Crash on memory access in non-readable regions
This patch makes it possible to make memory regions non-readable.
This is enforced using the "present" bit in the page tables.
A process that hits an not-present page fault in a non-readable
region will be crashed.
2019-12-02 19:18:52 +01:00

1.2 KiB

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.
  • -x: Read from recently freed memory. (Tests an opportunistic malloc guard.)
  • -y: Write to recently freed memory. (Tests an opportunistic malloc guard.)

Examples

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