docs: Add some .lldbint configurations for debugging document#3686
docs: Add some .lldbint configurations for debugging document#3686comphead merged 1 commit intoapache:mainfrom
Conversation
| use advanced `lldb` debugging. For example, we can ignore some exceptions and signals that are not relevant | ||
| to our debugging and would otherwise cause the debugger to stop. | ||
|
|
||
| ``` |
There was a problem hiding this comment.
Thanks @wForget is this example or recommended .lldbinit?
There was a problem hiding this comment.
I tend to think it is recommended, these exceptions/signals don't seem to need to be considered during local debugging.
|
|
||
| ``` | ||
| settings set platform.plugin.darwin.ignored-exceptions EXC_BAD_ACCESS|EXC_BAD_INSTRUCTION | ||
| process handle -n true -p true -s false SIGBUS SIGSEGV SIGILL |
There was a problem hiding this comment.
Do we really need to pass thru SIGBUS and SIGSEGV? The -Xint option to the JVM somewhat takes care of the signals that the JVM uses internally but even then I have seen SIGILL, BAD_ACCESS and BAD_INSTRUCTION but never encountered the other two.
We have hit SIGBUS and SIGSEGV in some of the Comet unsafe code though, iirc.
To be fair though, this is meant for advanced users who know what they are doing at that low a level, so maybe it is ok to include this in the recommendations.
There was a problem hiding this comment.
Do we really need to pass thru SIGBUS and SIGSEGV?
I'm not sure if I encountered it while debugging with Comet. I placed .lldbint in the USER_HOME directory and sometimes improved it while debugging Velox.
parthchandra
left a comment
parthchandra
left a comment
There was a problem hiding this comment.
Approved with comment
3 participants
Which issue does this PR close?
Closes #.
Rationale for this change
Avoid unnecessary debugger breaking
What changes are included in this PR?
Ignore some exceptions and signals on lldb debugger
How are these changes tested?