Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Crash in foo_input_std (Read 1962 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Crash in foo_input_std

Take a WAV file in WAVE_FORMAT_EXTENSIBLE format with wValidBitsPerSample == 20 and wBitsPerSample == 24.
Compress it to FLAC or Wavpack (cmdline encoders).

fb2k cannot verify integrity of such files: it crashes. No problems with the original WAV file though.

Crash in foo_input_std

Reply #1
This is most interesting, thanks for the report.
Microsoft Windows: We can't script here, this is bat country.


Crash in foo_input_std

Reply #3
I took Garbage sample from this thread and converted it to 3-bit pcm so it's possible to test various BitsPerSample / ValidBitsPerSample combinations: [attachment=7432:wValidBitsPerSample.7z]

fb2k 1.2.4 b1 doesn't crash but it doesn't cover some exotic cases (the result is MD5 mismatch for WavPack and Unsupported format or corrupted file for FLAC)

Crash in foo_input_std

Reply #4
Thanks for the detailed report.

FLAC with bit depth below 8 = fixed for the next update after 1.2.4 beta 3.
Exotic cases of WavPack bit depth configs (with 8 or more bits wasted) currently fail checksumming, I'll need to add special handling for these.
Microsoft Windows: We can't script here, this is bat country.