Skip to content

printing the log directly will obviously cause a JVM deadlock #821

Answered by apangin
hustchaya asked this question in Q&A
Discussion options

You must be logged in to vote

I'm not sure I understand the question. Are you talking about an existing async-profiler issue or you are trying to develop new functionality?

Since logging relies on *printf functions, it's unsafe to use it inside a signal handler.
See signal-safety(7) for the list of functions safe to call inside a signal handler.

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@hustchaya
Comment options

Answer selected by apangin
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants