Created attachment 87 [details] reproducer SHA1: d1f5de9f161b1b442b51f409c736b80c0d936755 Credit: Henri Salo from Nixu Corporation ./bin/gigdump ~/libgig-gigdump-segfault-PrintSamples-001.riff Global File Information: Total instruments: 1 Version: 3.0.305.41851 Name: 'Philharmonia Trumpet short loud' ArchivalLocation: ' ' CreationDate: '5/12/2009' Comments: 'Open Orchestra project' Product: 'http://sourceforge.net/projects/openorchestra/' Artists: 'London Philharmonia Orchestra' Genre: 'http://www.philharmonia.co.uk/thesoundexchange/' Engineer: 'Clement Guedez' Software: 'gigedit (linuxsampler project)' Medium: 'http://linuxsampler.org/' ALL defined Groups: Group 1) Name: "Trumpet short grp3" ALL Available Samples (as there might be more than referenced by Instruments): Sample 1) "E3_sm", Group 1, 44100Hz, 1 Channels, 0 Loops, crc=ffffffff, Length=11603 Compressed=false foffset=47788 fsz=23206 Sample 2) "F3_sl", Group 1, 44100Hz, 1 Channels, 0 Loops, crc=ffffffff, Length=8294 Compressed=false foffset=71202 fsz=16588 Sample 3) "A4_sl", Group 1, 44100Hz, 1 Channels, 0 Loops, crc=ffffffff, Length=11055 Compressed=false foffset=87998 fsz=22110 Sample 4) "Db4_sl", Group 1, 44100Hz, 1 Channels, 0 Loops, crc=ffffffffASAN:SIGSEGV ================================================================= ==453==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000010 (pc 0x00000040862f sp 0x7fffa4d77660 bp 0x7fffa4d77750 T0) #0 0x40862e in PrintSamples(gig::File*) /home/afl/src/libgig/src/tools/gigdump.cpp:236 #1 0x402f88 in main /home/afl/src/libgig/src/tools/gigdump.cpp:123 #2 0x7f5fffe75b44 in __libc_start_main (/lib/x86_64-linux-gnu/libc.so.6+0x21b44) #3 0x4037d9 (/home/afl/builds/libgig/2017-10-16/bin/gigdump+0x4037d9) AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV /home/afl/src/libgig/src/tools/gigdump.cpp:236 PrintSamples(gig::File*) ==453==ABORTING From quick look looks like only a tool issue so I put severity normal.
Does this problem still persist or can this report be closed?
I am going to close this report, since I received no further feedback from your side. Feel free to reopen this bug in case you think this issue persists.