Skip to content

Add FAQ about thread dumps in native reference guide #45467

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 10, 2025
Merged

Add FAQ about thread dumps in native reference guide #45467

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions docs/src/main/asciidoc/native-reference.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2301,6 +2301,19 @@ com.oracle.svm.core.VM=GraalVM 22.0.0.2-Final Java 11 Mandrel Distribution

See <<gc-logging,Native Memory Management GC Logging section>> for details.

=== Can I get a thread dump of a native executable?

Yes, Quarkus sets up a signal handler for the `SIGQUIT` signal (or `SIGBREAK` on windows) that will result in a thread
dump being printed when receiving the `SIGQUIT/SIGBREAK` signal.
You may use `kill -SIGQUIT <pid>` to trigger a thread dump.

[NOTE]
====
Quarkus uses its own signal handler, to use GraalVM's default signal handler instead you will need to:
1. Add `-H:+DumpThreadStacksOnSignal` to `quarkus.native.additional-build-args` and rebuild the application.
2. Set the environment variable `DISABLE_SIGNAL_HANDLERS` before running the app.
====

[[heap-dumps]]
=== Can I get a heap dump of a native executable? e.g. if it runs out of memory

Expand Down
Loading