program-analysis

It's nice if testing doesn't produce unnecessary artifacts after running with success but keeps relevant info on fail for further inspection.

Pytest should have a nice way of creating fixtures that can post-process a test based on whether it failed or not https://docs.pytest.org/en/latest/example/simple.html#making-test-result-information-available-in-fixtures

If a test fails, then keep the

I wrote some of the code to do this in a branch https://github.com/python-security/pyt/compare/class_based_views, but since I'm working on other things and this feature seems cool and important I'm making this issue 👍

Let me know if you would like any help in implementing.

It's common in various datasheets to have particular bits set, e.g. [0] - RST, [5-7] - MSK, [15-31] - DATA.

With long numbers, e.g. 64bit numbers, counting manually these bits is painful, and calling external commands, e.g. Python is suboptimal.

The idea is to allow a new bit mode for rz-ax that will print something like this:

$ rz-ax =2 0xb3
10110011b
$ rz-ax -B 0xb3
[0-1]: 1

I noticed you have a plugin for Ghidra, but it is not the only one FOSS tool available.
Rizin is a highly-portable cross-platform reverse engineering framework and a toolkit without dependencies. It has support for analyzing binaries, disassembling code, debugging programs, attaching to remote GDB/LLDB, WinDbg servers, rich plugin system (see rz-pm), and in

We should probably run go generate and other commands that generate code, such as goa gen, as part of our autobuilder.