Vector35 / Vector35/debugger

Unable to run TTD trace without network connection

Open
#568 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi,

I tried to run a WinDBG (TTD) execution trace in Binnary Ninja. I encountered an error when launching the trace in binary ninja.

Binja version: 4.1.5096-dev (69918583)
Documentation followed: https://docs.binary.ninja/guide/dbgeng-ttd.html#configure-the-ttd-trace-in-binary-ninja-debugger

WinDBG copied folder:
image

Working trace in WinDBG:
image

Binja Settings:
image

Debug Adapter Settings:
image

Crash during debugger launch in Binja:
image

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 with the linked TTD configuration documentation and reproduce the debugger launch with the network disconnected, using the reported Binary Ninja version and copied WinDBG folder. Compare the Binary Ninja and Debug Adapter settings shown in the report with the working WinDBG trace; done means an offline TTD trace launches without the reported crash.

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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.