-
Notifications
You must be signed in to change notification settings - Fork 236
Reporting Bugs
vadimcn edited this page Jun 21, 2023
·
8 revisions
- If the problem is related to core debugging functionality (e.g. erratic stepping), consider first trying to reproduce it with command-line LLDB. If it exhibits the same behavior, the problem is likely in LLDB itself, in which case I won't be able to do much about it (other than pulling in a newer version LLDB, where the problem had been fixed). Such cases would be better reported directly to LLDB developers.
A notable exception to this is anything related to Rust support, as it is added on top of the baseline LLDB. - A verbose log is often useful in deciphering what had happened during the debugging session.
- If possible, try to create a "minimal example" of code that reproduces your problem. It's always easier to diagnose problems when I can observe them live.
- Before hitting [Submit], please ask yourself whether you'd be able to reproduce the problem given the information you are about to submit. If not, the report likely won't be actionable without more details, so why not add them now?