Vector35 / Vector35/binaryninja-api

Need better support to map HLIL variables to MLIL variables

Open
#2,571 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Core Core: HLIL Impact: Medium
Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

Description

Inspecting the PossibleValueSet of variables in HLIL was not returning the expected results — I’m not sure about the specifics though or what should be done

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 examining the PossibleValueSet entry point and reproducing the reported mismatch when inspecting HLIL variables against MLIL variables. The issue names no files or tests, so first determine the relevant API and existing mapping behavior; done requires a clearly defined mapping and expected value results.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
reverse-engineering
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.