Your message dated Thu, 15 Jan 2015 23:41:58 +0100
with message-id <[email protected]>
and subject line Couldn't confirm the initial suspicion
has caused the Debian Bug report #772981,
regarding libvorbis: Suspicion of SIGFPE with corrupt input file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
772981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772981
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvorbis
Version: 1.3.4-2
Severity: normal
While investigating the cause for #772978, the relevant libvorbis code
gave me the impression that (with input files different from the
referenced one) the division by zero may happen even if oggdec handled
the reported errors correctly.
The relevant stacktrace:
Process terminating with default action of
signal 8 (SIGFPE)
Integer divide by zero at address 0x802FA8133
at 0x50632A6: res2_inverse (res0.c:830)
by 0x50654A8: mapping0_inverse (mapping0.c:756)
by 0x5054071: vorbis_synthesis (synthesis.c:88)
by 0x4E3AC66: _fetch_and_process_packet
(vorbisfile.c:707)
by 0x4E3E073: ov_read_filter (vorbisfile.c:1971)
by 0x4E3E6D2: ov_read (vorbisfile.c:2092)
by 0x40212A: decode_file (oggdec.c:304)
by 0x402692: main (oggdec.c:455)
I am going to look for other ways (not exploiting oggdec's poor error
handling) to trigger this division by zero and report it back here.
Cheers,
Martin
--- End Message ---
--- Begin Message ---
Couldn't confirm my initial suspicion, looks like all the necessary
guards are in place to prevent the SIGFPE in a regular case (without
problems in the calling library like in #772978). So I'm closing this
report.
--- End Message ---
