Results for: stuff

...DDD has become famous through its interactive graphical data display, where data structures are displayed as graphs. You can support the principle of software freedom by buying stuff from the FSF shop. To run DDD, you need the GNU debugger (GDB), version 4.16 or later (or depending on the program to be debugged, possibly other command-line debuggers such as Ladebug, JDB, XDB, the Perl debugger, the bash debugger bashdb, the GNU Make debugger remake, or the Python debugger pydb).

The IP class allows a comfortable parsing and handling for most notations in use for IPv4 and IPv6 addresses and networks. It was greatly inspired by RIPE’s Perl module NET::IP’s interface but doesn’t share the implementation. It doesn’t share non-CIDR netmasks, so funky stuff like a netmask of 0xffffff0f can’t be done here. It can detect about a dozen different ways of expressing IP addresses and networks, parse them and distinguish between IPv4 and IPv6 addresses. Nearly all class methods which return a string have an optional parameter ‘wantprefixlen’ which controls if the prefixlen or netmask is printed. ...

waiting is a small library for waiting for stuff to happen. It basically waits for a function to return True, in various modes. Waiting is compatible with flux for simulated timelines. The most basic usage is when you have a function you want to wait for. Waiting forever is very simple. If your predicate returns a value, it will be returned as the result of wait(). A timeout parameter can also be specified.

This plugin produces coverage reports. Compared to just using coverage run this plugin does some extras. Subprocess support, so you can fork or run stuff in a subprocess and will get covered without any fuss. Xdist support, so you can use all of pytest-xdist’s features and still get coverage. Consistent pytest behavior. All features offered by the coverage package should work, either through pytest-cov’s command line options or through coverage’s config file. Under certain scenarios, a stray .pth file may be left around in site packages. ...

...The Unicorn-based test harness loads the target code, sets up the initial state, and loads in data mutated by AFL from disk. The test harness then emulates the target binary code, and if it detects that a crash or error occurred it throws a signal. AFL will do all its normal stuff, but it’s actually fuzzing the emulated target binary code. Only tested on Ubuntu 16.04 LTS, but it should work smoothly with any OS capable of running both AFL and Unicorn.