Vector35 / Vector35/debugger

dbg magic variable not available in snippets

Open
#666 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Version and Platform (required):

  • Binary Ninja Version: 6473
  • OS: windows
  • OS Version: 24h2
  • CPU Architecture: x64
  • Local or Remote Debugging: local

Bug Description:
the magic dbg variable is not available via snippets

Steps To Reproduce:
Please provide all steps required to reproduce the behavior:

  1. create a new snippet
  2. print(dbg.regs['rip'])
  3. see error

Expected Behavior:
it prints rip

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

Reproduce the issue by creating a new snippet and running print(dbg.regs['rip']) on the reported Windows Binary Ninja setup. Trace how snippet execution receives its context and make dbg.regs['rip'] available so the snippet prints the instruction pointer without an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devtools, reverse-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.