luo980/cpptrace
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Explain the purpose of raw trace information vs minimal object frame info

Browse Source
This commit is contained in:
Jeremy 2023-11-20 22:49:07 -06:00
parent a6a64b5671
commit a04f19a484
No known key found for this signature in database
GPG Key ID: B4C8300FEC395042
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
signal-safe-tracing.md
View File

@ -56,6 +56,14 @@ namespace cpptrace {
} }
``` ```
`safe_generate_raw_trace` produces instruction pointers found while unwinding the stack. These addresses are sufficient
information to resolve a stack trace in the currently running process after a signal handler exits, but they aren't
sufficient for resolving outside of the currently running process, unless there is no position-independent code or
shared-library code.
To resolve outside the current process `minimal_object_frame` information is needed. This contains the path to the
object where the address is located as well as the address before address randomization.
# Strategy # Strategy
Signal-safe tracing can be done three ways: Signal-safe tracing can be done three ways: