-
Updated
Jun 4, 2022 - OCaml
program-analysis
Here are 153 public repositories matching this topic...
-
Updated
Jun 2, 2022 - JavaScript
-
Updated
May 30, 2022 - Python
-
Updated
Jun 4, 2022 - C++
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.
-
Updated
May 10, 2022 - C++
-
Updated
Jun 4, 2022 - OCaml
Work environment
| Questions | Answers |
|---|---|
| OS/arch/bits (mandatory) | Fedora 35 x86_64 |
| File format of the file you reverse (mandatory) | - |
| Architecture/bits of the file (mandatory) | - |
rizin -v full output, **not trunc |
-
Updated
Jun 4, 2022 - C++
-
Updated
Jun 2, 2022 - Python
Some places use D and some use d_t. We should just pick some to standardize on the template type name.
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
-
Updated
Mar 25, 2022 - Roff
-
Updated
Apr 7, 2022 - Java
-
Updated
May 10, 2022 - Rust
-
Updated
May 17, 2022 - CodeQL
-
Updated
Jun 3, 2022 - C++
-
Updated
Dec 28, 2021 - Kotlin
-
Updated
Jun 4, 2022 - Java
-
Updated
May 30, 2022 - C++
-
Updated
Jun 2, 2022 - C
-
Updated
Jul 10, 2018 - Scala
-
Updated
May 14, 2022 - Java
-
Updated
Nov 24, 2021 - Scala
-
Updated
Jun 3, 2022 - C
-
Updated
Jul 18, 2020 - Java
-
Updated
Jun 3, 2022 - C++
-
Updated
May 23, 2022 - Rust
Improve this page
Add a description, image, and links to the program-analysis topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the program-analysis topic, visit your repo's landing page and select "manage topics."


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