| Age | Commit message (Collapse) | Author |
|---|
|
matched functions
One day I will get the QT incantations correct
|
|
guids generated
Just a sanity check so we can alert the user, they can just reanalyze their functions and the guid will be constructed
|
|
We emit jumps at the end of some blocks that the architecture is not aware of, they are not actually apart of the functions instructions
rather they are used in our analysis... somehow, I have not figured out what they are supposed to be used for but regardless, they should be
ignored by WARP.
This was just a case where the filtering was including jumps in non start instructions, where we actually wanted the opposite.
|
|
This removes more barriers for those working with firmware to use WARP, previously if you had defined any sections (such as a vector interrupt table) then backed segments would
end up being marked non-relocatable. This, combined with the use of ELF intermediate object files created inconsistent GUID's, using the segments backing the real functions fixes this.
|
|
|
|
|
|
|
|
during analysis
|
|
|
|
It is apparently "too bright" and I need to get "my eyes checked"
|
|
|
|
- Fix cmake clean not cleaning target docs
- Fix not prioritizing enterprise remote in collab tests
- Some misc formatting
- Fix incorrect assert in binary loading
|
|
|
|
wants the symbol
We were previously constructing the function type, comments and variables to just throw away, wasting precious cpu cycles!
|
|
Will also adjust the worker thread count so that there is enough for view destruction and what not.
The default will be filled as well for the user.
|
|
Just added noise to the logs, probably should do this for rtti as well
|
|
|
|
|
|
|
|
|
|
|
|
|
|
of references
|
|
|
|
|
|
This reverts commit 5d92c427fdb16e0b167b88eb53f61693cd67c535.
|
|
|
|
|
|
|
|
|
|
Don't add an additional reference to the wrapped object in the
constructor.
API wrapper objects are passed a +1 object and do not need to add an
additional reference. All clients of the Workflow constructors are doing
this already which was resulting in leaks.
Fixes https://github.com/Vector35/binaryninja-api/issues/7059.
|
|
|
|
|
|
|
|
than the item limit but still not a complete list. Add the + indicator on the other categories if this condition is detected.
|
|
|
|
|
|
|
|
- Fix project file filter not blacklisting warp files
- Fix project name not being used for default file save name
- Prevent adding the same file to the available sources
|
|
This previously was not allowed as the information would sometimes include a zero based segment, however this is still preferable in the case of firmware, where sections will not be available by default. This improves the usability of WARP with firmware by removing the requirement of filling section information prior to function analysis.
|
|
This is going to be disabled by default on this upcoming stable, however users may enable it once we deploy the public server. The data from the server is done through `Container::fetch_functions` independent of the nonblocking function lookup functions.
The sidebar has been updated to drive fetching so that when users navigate to a new function the fetcher will kick off. This fetcher operates on a separate thread, in the event of a user navigating to many functions before the current fetch has completed they all will be batched together in a single fetch.
Networked container currently is limited to just function prototypes, other type information separate from the function object will be omitted.
|
|
|
|
Previously we only really had a way to access the platform system call information, this was missing the system call information found in type libraries
Fixes https://github.com/Vector35/binaryninja-api/issues/7089
|
|
|
|
|
|
|
|
|
|
|
|
Was previously not exposed, we want it for unit tests.
|
|
With the new instruction retrieval we are getting the instructions at the end of the lifted function which are not really apart of the function, but they share the address of the last ret/jump.
|
