DbgEng adapter does not work if one first uses LLDB adapter to debug on Windows
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 331
- Forks
- 33
- PR merge metrics
- No merged PRs in 30d
Description
Using the LLDB adapter will cause the liblldb.dll to be loaded, which then loads the sytem32 dbgeng DLLs. They are incompatible with the ones the debugger uses. Pretty similar to https://github.com/Vector35/debugger/issues/343.
I have noticed this issue earlier and I have made a mitigation for this. I made the liblldb.dll is delay-loaded. Otherwise, the situation would be worth: liblldb.dll will be loaded on BN startup, which renders DbgEng adapter totally unusable.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing this report with issue 343 and tracing how the LLDB adapter loads liblldb.dll and how that interacts with the DbgEng adapter on Windows. Done means using the LLDB adapter first no longer prevents the DbgEng adapter from working, while preserving the reported startup mitigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100