Bug 40236

Summary: [1.0-rc2] paplay 8k16bitpcm.wav crashes
Product: PulseAudio Reporter: Jan Willies <jan>
Component: toolsAssignee: pulseaudio-bugs
Status: RESOLVED NOTOURBUG QA Contact: pulseaudio-bugs
Severity: normal    
Priority: medium CC: colin, lennart
Version: unspecified   
Hardware: Other   
OS: All   
i915 platform: i915 features:
Attachments: config.log output

Description Jan Willies 2011-08-19 07:32:00 UTC
Index: pulseaudio-0.99.2/src/pulsecore/sndfile-util.c
--- pulseaudio-0.99.2.orig/src/pulsecore/sndfile-util.c 2011-08-08 14:45:43.000000000 +0200
+++ pulseaudio-0.99.2/src/pulsecore/sndfile-util.c      2011-08-19 15:31:22.000000000 +0200
@@ -39,7 +39,11 @@
-    pa_assert_se(sf_command(sf, SFC_GET_CURRENT_SF_INFO, &sfi, sizeof(sfi)) == 0);
+    int sf_errno;
+    sf_errno = sf_command(sf, SFC_GET_CURRENT_SF_INFO, &sfi, sizeof(sfi));
+    pa_log("sndfile error: %s", sf_error_number(sf_errno));
+    pa_assert(sf_errno == 0);
     switch (sfi.format & SF_FORMAT_SUBMASK) {

After applying this patch I get:

root@OpenWrt:/# paplay /etc/8k16bitpcm.wav
sndfile error: Bad parameter passed to function sf_command.
Assertion 'sf_errno == 0' failed at pulsecore/sndfile-util.c:46, function pa_sndfile_read_sample_spec(). Aborting.

I am using libsndfile-1.0.25
Comment 1 Jan Willies 2011-08-19 07:54:26 UTC
Created attachment 50377 [details]
config.log output
Comment 2 Colin Guthrie 2011-08-20 11:54:11 UTC
Can you post the file somewhere (or send it to me privately)?

I tried googling for that filename but only found one that worked....

So perhaps it's a bad file or similar - obviously doesn't happen across the board.

I'm also using that same version of libsndfile
Comment 3 Jan Willies 2011-08-21 23:54:03 UTC
Ok, it turned out this is no bug in PA. It was libsndfile which was compiled without large file support because of some wrong autotool stuff. Thanks to mkbosmans for giving the hints. 
I'll file a bug against libsndfile now, this can be closed.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.