Control: reopen -1
Control: forwarded -1 https://github.com/soedinglab/ffindex_soedinglab/issues/7
Since we really want this code base I need to re-open the bug which is not
solved.
In a gdb session I've found the actual code line which causes the SIGSEGV:
ffindex_build -s ./test.data ./test.ffindex test/data test/data2
ffindex_get ./test.data ./test.ffindex a b foo | tee ./test.out
a
bb
fooo
fooo
gdb --args ffindex_modify -u ./test.ffindex b
GNU gdb (Debian 8.2-1) 8.2
...
(gdb) break src/ffindex.c:553
Breakpoint 1 (src/ffindex.c:553) pending.
(gdb) run
Starting program: ffindex_modify -u ./test.ffindex b
Breakpoint 1, action (node=0x555555559801, which=postorder, depth=1,
misc=0x555555559260) at
/build/ffindex-0.9.9.7.soedinglab+git20171201.74550c8/src/ffindex.c:553
553 entry = *(ffindex_entry_t **) node;
(gdb) print entry
$1 = (ffindex_entry_t *) 0x7
(gdb) print entry->offset
Cannot access memory at address 0x7
(gdb) next
554 if(fprintf(index_file, "%s\t%zd\t%zd\n", entry->name,
entry->offset, entry->length) < 0)
(gdb) next
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7f7bc6d in action (node=0x555555559801, which=postorder,
depth=1, misc=0x555555559260) at
/build/ffindex-0.9.9.7.soedinglab+git20171201.74550c8/src/ffindex.c:554
554 if(fprintf(index_file, "%s\t%zd\t%zd\n", entry->name,
entry->offset, entry->length) < 0)
I'll keep on discussing this with upstream.
Kind regards
Andreas.
--
http://fam-tille.de
