==26039== Memcheck, a memory error detector
==26039== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==26039== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==26039== Command: ./boolector-plain pusht_bfr.btor2
==26039==
==26039== Warning: set address range perms: large range [0x15bf0028, 0x25bf0058) (noaccess)
==26039== Warning: set address range perms: large range [0x79e43040, 0x99e43040) (undefined)
==26039== Warning: set address range perms: large range [0x25bf1028, 0x45bf1058) (noaccess)
==26039== Warning: set address range perms: large range [0xd9e44040, 0x119e44040) (undefined)
==26039== Warning: set address range perms: large range [0x59e43028, 0x99e43058) (noaccess)
==26039== Warning: set address range perms: large range [0x199e45040, 0x219e45040) (undefined)
==26039== Warning: set address range perms: large range [0x99e44028, 0x119e44058) (noaccess)
==26039== Warning: set address range perms: large range [0x319e46040, 0x419e46040) (undefined)
==26039== Warning: set address range perms: large range [0x119e45028, 0x219e45058) (noaccess)
==26039== Warning: set address range perms: large range [0x619e47040, 0x819e47040) (undefined)
==26039== Warning: set address range perms: large range [0x219e46028, 0x419e46058) (noaccess)
==26039== Invalid write of size 8
==26039== at 0x1197DA: pusht_bfr (in /home/user/boolector-plain)
==26039== by 0x11991C: new_line_bfr (in /home/user/boolector-plain)
==26039== by 0x1E9730: btor2parser_read_lines (in /home/user/boolector-plain)
==26039== by 0x1BB013: parse_btor2_parser (in /home/user/boolector-plain)
==26039== by 0x16C6FD: btor_parse (in /home/user/boolector-plain)
==26039== by 0x128F87: boolector_main (in /home/user/boolector-plain)
==26039== by 0x541AB96: (below main) (libc-start.c:310)
==26039== Address 0x400000000 is 8,155,537,344 bytes inside a block of size 8,589,934,592 free'd
==26039== at 0x4C31D2F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26039== by 0x1197C5: pusht_bfr (in /home/user/boolector-plain)
==26039== by 0x11991C: new_line_bfr (in /home/user/boolector-plain)
==26039== by 0x1E9730: btor2parser_read_lines (in /home/user/boolector-plain)
==26039== by 0x1BB013: parse_btor2_parser (in /home/user/boolector-plain)
==26039== by 0x16C6FD: btor_parse (in /home/user/boolector-plain)
==26039== by 0x128F87: boolector_main (in /home/user/boolector-plain)
==26039== by 0x541AB96: (below main) (libc-start.c:310)
==26039== Block was alloc'd at
==26039== at 0x4C31D2F: realloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==26039== by 0x1197C5: pusht_bfr (in /home/user/boolector-plain)
==26039== by 0x11991C: new_line_bfr (in /home/user/boolector-plain)
==26039== by 0x1E9730: btor2parser_read_lines (in /home/user/boolector-plain)
==26039== by 0x1BB013: parse_btor2_parser (in /home/user/boolector-plain)
==26039== by 0x16C6FD: btor_parse (in /home/user/boolector-plain)
==26039== by 0x128F87: boolector_main (in /home/user/boolector-plain)
==26039== by 0x541AB96: (below main) (libc-start.c:310)
==26039==
boolector: line 5: expected tag
==26039==
==26039== HEAP SUMMARY:
==26039== in use at exit: 17,179,869,328 bytes in 3 blocks
==26039== total heap usage: 870 allocs, 867 frees, 68,719,507,815 bytes allocated
==26039==
==26039== LEAK SUMMARY:
==26039== definitely lost: 120 bytes in 1 blocks
==26039== indirectly lost: 24 bytes in 1 blocks
==26039== possibly lost: 17,179,869,184 bytes in 1 blocks
==26039== still reachable: 0 bytes in 0 blocks
==26039== suppressed: 0 bytes in 0 blocks
==26039== Rerun with --leak-check=full to see details of leaked memory
==26039==
==26039== For counts of detected and suppressed errors, rerun with: -v
==26039== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Used version
$ boolector --version
3.0.1-pre
Steps to reproduce
boolector pusht_bfr.btor2.txt
The text was updated successfully, but these errors were encountered:
While fuzzing boolector,
this input file
The attached file contains more lines leading to the same crash, the above file contains the minimal version.
ASAN trace (probably not useful, since it does not find the write)
Valgrind trace
Used version
Steps to reproduce
The text was updated successfully, but these errors were encountered: