Skip to content

Signal handlers

Jump to bottom
mhahnFr edited this page Jul 4, 2025 · 4 revisions

The LeakSanitizer catches deadly signals.

Deadly signals

Upon receipt of a deadly signal, the program is terminated and the callstack of the receiving point is printed. The faulty address is also printed if available.

Tip

Example: Example stacktrace of a segmentation fault

Caught deadly signals

  • SIGSEGV
  • SIGABRT
  • SIGTERM
  • SIGALRM
  • SIGPIPE
  • SIGFPE
  • SIGILL
  • SIGQUIT
  • SIGHUP
  • SIGBUS
  • SIGXFSZ
  • SIGXCPU
  • SIGSYS
  • SIGVTALRM
  • SIGPROF
  • SIGTRAP

SIGUSR1

SIGUSR1 causes the current memory statistics to be printed. It shows you the amount of the currently allocated objects and the amount of the currently allocated bytes as well as their peek values.

These statistics are only available if the statistical bookkeeping is activated by LSAN_AUTO_STATS or LSAN_STATS_ACTIVE.

Tip

Example: Example statistics

SIGUSR2

SIGUSR2 causes the stacktrace of the signal handler to be printed.

Tip

Example: Example stacktrace

Copyright (C) 2022 - 2025 mhahnFr.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License.

Clone this wiki locally