Bug#818037: vorbis-tools: vcut always(?) segfaults

[Petter Reinholdtsen]

[Frank Heckenbach]
> Sorry for the brief description, but for what I can tell, that's
> really it. I tried various cases, and vcut always seems to just
> segfault. Here's one example:
>
> % head -c 500000 /dev/zero | oggenc -Q -r -o 1.ogg -
> % vcut 1.ogg 2.ogg 3.ogg +1
> Processing: Cutting at 1,000000 seconds
> Segmentation fault

I see the same, and this is the output from valgrind:

% valgrind vcut 1.ogg 2.ogg 3.ogg +1
==27037== Memcheck, a memory error detector
==27037== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==27037== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==27037== Command: vcut 1.ogg 2.ogg 3.ogg +1
==27037== 
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/ld-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libc-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- Ignoring non-Dwarf2/3/4 block in .debug_info
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- Last block truncated in .debug_info; ignoring
--27037-- WARNING: Serious error when reading debug info
--27037-- When reading debug info from /lib/x86_64-linux-gnu/libm-2.22.so:
--27037-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4
Processing: Cutting at 1.000000 seconds
==27037== Invalid read of size 1
==27037==    at 0x4C2E7E6: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:1018)
==27037==    by 0x5064202: ogg_stream_iovecin (in /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==    by 0x506435B: ogg_stream_packetin (in /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==    by 0x401A4D: ??? (in /usr/bin/vcut)
==27037==    by 0x401BDB: ??? (in /usr/bin/vcut)
==27037==    by 0x402029: ??? (in /usr/bin/vcut)
==27037==    by 0x4023BA: ??? (in /usr/bin/vcut)
==27037==    by 0x4025C2: ??? (in /usr/bin/vcut)
==27037==    by 0x4014F7: ??? (in /usr/bin/vcut)
==27037==    by 0x528B60F: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so)
==27037==  Address 0xfff001000 is not stack'd, malloc'd or (recently) free'd
==27037== 
==27037== 
==27037== Process terminating with default action of signal 11 (SIGSEGV)
==27037==  Access not within mapped region at address 0xFFF001000
==27037==    at 0x4C2E7E6: memcpy@@GLIBC_2.14 (vg_replace_strmem.c:1018)
==27037==    by 0x5064202: ogg_stream_iovecin (in /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==    by 0x506435B: ogg_stream_packetin (in /usr/lib/x86_64-linux-gnu/libogg.so.0.8.2)
==27037==    by 0x401A4D: ??? (in /usr/bin/vcut)
==27037==    by 0x401BDB: ??? (in /usr/bin/vcut)
==27037==    by 0x402029: ??? (in /usr/bin/vcut)
==27037==    by 0x4023BA: ??? (in /usr/bin/vcut)
==27037==    by 0x4025C2: ??? (in /usr/bin/vcut)
==27037==    by 0x4014F7: ??? (in /usr/bin/vcut)
==27037==    by 0x528B60F: (below main) (in /lib/x86_64-linux-gnu/libc-2.22.so)
==27037==  If you believe this happened as a result of a stack
==27037==  overflow in your program's main thread (unlikely but
==27037==  possible), you can try to increase the size of the
==27037==  main thread stack using the --main-stacksize= flag.
==27037==  The main thread stack size used in this run was 8388608.
==27037== 
==27037== HEAP SUMMARY:
==27037==     in use at exit: 97,967,813 bytes in 116 blocks
==27037==   total heap usage: 121 allocs, 5 frees, 97,996,535 bytes allocated
==27037== 
==27037== LEAK SUMMARY:
==27037==    definitely lost: 0 bytes in 0 blocks
==27037==    indirectly lost: 0 bytes in 0 blocks
==27037==      possibly lost: 0 bytes in 0 blocks
==27037==    still reachable: 97,967,813 bytes in 116 blocks
==27037==         suppressed: 0 bytes in 0 blocks
==27037== Rerun with --leak-check=full to see details of leaked memory
==27037== 
==27037== For counts of detected and suppressed errors, rerun with: -v
==27037== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault
%

-- 
Happy hacking
Petter Reinholdtsen