-
Notifications
You must be signed in to change notification settings - Fork 261
Open
Labels
Component: WARPEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: HighIssue adds or blocks important functionalityIssue adds or blocks important functionality
Milestone
Description
Version and Platform (required):
- Binary Ninja Version: 5.2.8109-dev Ultimate, c239cc75
- OS: macos
- OS Version: 15.6
- CPU Architecture: x86_64
Bug Description:
Nothing but the symbol name itself is working when using a WARP signature file in the user's sig folder on a newly opened and analyzed file. WARP is naming the functions, making a symbol, making the WARP tag, and nothing else. No types, no function signatures, nothing but the name.
Steps To Reproduce:
- Opem this project: "elegant ninja channels swiftly"
- Open this database: /NSIS/Version 1/Release/1.0f/Base/nsis10f.exe/exehead_1.0f.bndb
- Plugins Menu > WARP > Create > From Current View
- Keep the path of the sig where it defaults to in the user's sig folder, but change the name of the sig to nsis_1.0f.warp
- Make sure File Data is set to All
- Include Functions: Annotated
- Generate Report: HTML
- Click OK
- Close binary ninja
- Open binary ninja
- Open project
- Open this file as a new database: /NSIS/Version 1/Release/1.0f/Base/nsis10f.exe (this file has the exact same exehead as the template exehead, so all functions will match).
- After all the analysis is complete you will see that WARP named all the functions.
- Navigate to any function, this one is a good one to look at:
inflate_codes_newbecause it should have types and parameter names and the function signature etc.
Expected Behavior:
Function signature and types applied as expected not just function name.
Metadata
Metadata
Assignees
Labels
Component: WARPEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: HighIssue adds or blocks important functionalityIssue adds or blocks important functionality


