Vector35 / Vector35/debugger

Bug: WindDbg integration not working

Open
#433 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug DbgEng Adapter Impact: Medium
Dominant language
C++
Stars
331
Forks
33
PR merge metrics
No merged PRs in 30d

Description

For me the WinDbg integration is not working. I tried this on the mainline version and in dev as well. I tired also to Reinstall DbgEng Redistributable which didn't make any difference.

Sample output below of spawning a process to debug:
image

Loaded signature library: C:\Users\b33f\tools\BinaryNinja\signatures\windows-x86_64\msvcrt_windows-x86_64.sig
Loaded signature library: C:\Users\b33f\tools\BinaryNinja\signatures\windows-x86_64\ucrt_windows-x86_64.sig
59 functions matched total, 0 name-only matches, 0 thunks resolved, 67 functions skipped because they were too small
Analysis update took 8.620 seconds
No available/valid debug info parsers for `Raw` view
Analysis update took 0.013 seconds
Analysis update took 0.000 seconds
Analysis update took 0.000 seconds
Analysis update took 0.000 seconds
Analysis update took 0.000 seconds
Analysis update took 0.000 seconds
Failed to load dbgeng.dll, 127
Failed to connect process server

It looks ok on the filesystem.

image

Binary Ninja Version: 3.4.4080-dev Personal, 842d9298
Platform: Windows 11 Version 21H2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure on Windows 11 using the reported Binary Ninja version and DbgEng Redistributable, then investigate the Failed to load dbgeng.dll, 127 and Failed to connect process server messages. Done means the WinDbg integration loads successfully and can connect to a spawned process.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
operating-systems, reverse-engineering
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.