Vector35 / Vector35/binaryninja-api
Unable to create ExternalSymbols in non-PE views
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 4.1.5403-dev Personal (45205530)
- OS: Ubuntu Linux
- OS Version: 22.04
- CPU Architecture: x64
Bug Description:
When in a non-PE view, symbols of type ExternalSymbol will not get created.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- In an ELF view or empty file create a section with
SectionSemantics.ExternalSectionSemantics - Define a symbol in that section with
SymbolType.ExternalSymbol - The log will output an analysis update, but the symbol does not render in the view. It seems like it doesn't get created in any way.
Expected Behavior:
I would expect an ExternalSymbol to be created and rendered in the section. If doing the above steps on a PE binary, you get the expected results.
Additional Information:
Doing these steps through the API or GUI gives the same results. This is also the same result if created with define_auto_symbol or define_auto_symbol_and_var_or_function
I maintain binaryninja-xbe which loads PE-like binaries
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in an ELF view or empty file by creating an external section and defining an ExternalSymbol through the API or GUI. Start with define_auto_symbol and define_auto_symbol_and_var_or_function, then compare non-PE behavior with a PE view. Done means the ExternalSymbol is created and rendered in the section for non-PE views.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, reverse-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100