Optionally use demangled names in WARP file creation

Open
#7,193 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue does not name a file, test, or entry point. Start by locating WARP file creation and the consumer code that demangles stored names, then determine whether an optional demangled-name setting and its deduplication behavior can be specified consistently.

Written by the indexing model from the issue text.

Description

Component: WARP Effort: Trivial Impact: Low

Currently mangled names are stored in the WARP file and we expect consumers to demangle them, this is because we may pull information like types from the symbol itself rather than storing the type object seperately, saving some space in the file.

However if we demangled the name and then stored that we could have better deduplication, depending on if we care about the demangled type information.

Opening for discussion, I am not particularly for/against it and making it a setting likely would not be difficult, just need to make sure that the behavior of it makes sense.

Dominant language
C++
Stars
1.3k
Forks
298
Avg merge
5d 5h
Merged PRs (30d)
19

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.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.