Can we have a feature where a normal brute force is running based on HTTP response like 403/401 do a recursive brute force on that endpoint?

When the computer is suspended during a fuzzing session, the time spent in suspended state is counted as a "run time" on a statistics screen. In case fuzzing was running for several hours and then the computer was suspended for several more hours, on one hand I would prefer not restarting the session, on the other hand, now it may be harder to tell how well a harness performs (corpus count vs. run

We can safely disallow any use of solc below 0.4.25.

If I remember correctly, I wasn't able to implement on-demand paging with whv because doing a WHvTranslateGva with an empty environment doesn't generate memory faults like executing would.

This is annoying because wtf does memory translation to be able to set breakpoints where the user wants to; to do that it needs to do a VirtTranslate so I ended up mapping it all at start-up. It's not ide

All the tools in prjxray should have an xc7 prefix, so to make them unique.

E.g. bitread or bittool could enter in conflicts with other tools names.

Feature request

Is your feature request related to a problem? Please describe

The analysis.py script provides just one confidence interval: 95%. While that is related to the 2-sigma interval of normal distribution, so in theory allows for easy estimation of bigger confidence intervals (like 3, 4, 5-sigma), it assumes a normal distribution, which the differences don't follow, and may be