Linux specific: Give access to siginfo_t in signalHandler() #541
Labels
Comments
ablangy
added a commit
to ablangy/g3log
that referenced
this issue
Jan 13, 2025
By using some informations located in siginfo_t for tracing, it remain accessible to be inspected by debugger even if the code compiled with optimisation flags (typically -O2).
7 tasks
KjellKod
pushed a commit
that referenced
this issue
Jan 17, 2025
|
Resolved with PR #542 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, the informations located in the
siginfo_tstructure are not used by this handler.The bad effect is that when g3log is compiled with some optimisation flags, those data are not available to be inspected with the debugger because they are drop away.
In some situation, it is good to know the si_code provided by the system or the faulty address.
Describe the solution you'd like
By printing some more information like
info.si_codeandinfo.si_errnoin the backtrace's output, we can save time and be able to access the othersiginfo_tinformations with the debugger.Describe alternatives you've considered
I consider the possibility to not use this signal handler and write a custom one.
The needed modifications to have
signalHandler()provide thesesiginfo_tinformations are really minors and IMHO those informations can be useful to someone else.The text was updated successfully, but these errors were encountered: