| Age | Commit message (Collapse) | Author |
|---|
|
Its not critical, but I still want it to be visible when it fails
|
|
|
|
[ARM64] remove zero extend from ubfx, ubfiz
[ARM64] only zero extend fmov when needed
arm64: resolve ambiguity
Resolves #7307
|
|
|
|
|
|
|
|
|
|
Loggers are not owned by a specific thread and many are used by multiple threads. The indenting APIs could not be made to be thread safe in any way as they exist, so they have been removed. The data races caused by the indenting APIs are actually an important stability issue that could cause the indentation level to go out of bounds and crash the product.
If you were using the indentation APIs, you will need to rewrite the usage to manually manage the indentation level in a thread safe way.
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/7266
|
|
correspond to
|
|
The down and enter keys now preserve an existing selection in the
associated list or table views, rather than unconditionally selecting or
activating the first item.
|
|
|
|
|
|
|
|
Removes the need to book keep on the caller side
|
|
This allows connections to enterprise servers without requiring the default download provider to be switched in settings
|
|
|
|
clarify `bit_position`
This is a helper because it is likely one dealing with bitfields knows the bit offset, rather than the bit position, so this can be used instead.
|
|
|
|
of signed hints in casts
|
|
|
|
|
|
This reverts commit 72fcf44f3731ade3cf1310da55f633f1cb9069ce.
|
|
|
|
|
|
|
|
|
|
|
|
through the Container Browser dialog.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
