This release is a pre-release and may not be stable for production use.
ddSMT
ddSMT is a delta debugger for Sat Modulo Theories (SMT) benchmarks in SMT-LIB v2 format. It serves as an input minimizer for SMT benchmarks on which a given executable shows unexpected or faulty behavior and supports all SMT-LIB v2 logics. For more details on the SMT-LIB v2 format see [1].
ddSMT is implemented in Python 3 and developed on a Linux OS. ddSMT requires Python version 3.2 or later. Note that due to major improvements with respect to the internal string representation in Python 3.3 (see [2]) it is strongly recommended to use Python version 3.3 or later.
ddSMT is free software released under the GPLv3. You should have received a copy of the GNU General Public License along with ddSMT (see file COPYING). If not, see [3].
Download:
The latest version of ddSMT can be found on GitHub: https://github.com/aniemetz/ddSMT
Usage:
ddSMT minimizes a failure-inducing input in SMT-LIB v2 format based on the exit code and the error output of a given command when executed on that input.
Note that ddSMT supports on-the-fly input minimization, i.e. as soon as an input minimization was successful it is available as the output file specified. Hence, it is not necessary to wait for ddSMT until completion, which can be useful for hard to minimize input files with long solver execution times.
Invocation:
/path/to/ddsmt.py [<options>] <infile> <outfile> <cmd> [<cmd options>]
Positional arguments:
infile: the input file in SMT-LIB v2 format
outfile: the outputfile
cmd: the command to be executed (with optional arguments)
Optional arguments:
-h, --help show this help message and exit
-t val timeout for test runs in seconds (default: none)
-v increase verbosity
-o use err exit code only to identify failing input
(default: error exit code AND stderr output)
--version show program's version number and exit
References:
[1] http://www.smtlib.org
[2] http://docs.python.org/3/whatsnew/3.3.html#pep-393
[3] http://www.gnu.org/licenses/
Release files for ddSMT 0.1.dev368
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| ddSMT-0.1.dev368.tar.gz | 34.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ddSMT-0.1.dev368-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 75.9 kB
Release files / ddSMT-0.1.dev368.tar.gz
| Download URL | ddSMT-0.1.dev368.tar.gz |
|---|---|
| Size | 34.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
467393dcdbc3711e4843b198dd779920f042b08ec60a5edf7c0d51dd91b643a1
|
|
BLAKE2b-256 checksum How to use checksums |
1f6bb249be334cdfea98ac254aefa1716c4e4048bd67451758a10764726f04ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.9.1
|
Release files / ddSMT-0.1.dev368-py3-none-any.whl
| Download URL | ddSMT-0.1.dev368-py3-none-any.whl |
|---|---|
| Size | 41.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9a240bc633fdc72fa7a7ff129f41fca96bd168f06fd91e9d55301846b8627d37
|
|
BLAKE2b-256 checksum How to use checksums |
245bf67c6db63c49a0ae2911b518016f375bb646e7a4526042279bfb79f6763a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.6.1 requests/2.25.1 setuptools/49.2.1 requests-toolbelt/0.9.1 tqdm/4.55.1 CPython/3.9.1
|
Security for ddSMT 0.1.dev368
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
