Package: libportaudio0
Version: 18.1-2
Severity: important

As called from iaxcomm, the library writes to stdout

  PortAudio: read interrupted!

repeatedly, at a great rate, until killed.  iaxcomm operation appears 
to be affected by this only in that no audio is delivered to the other 
party to a call, and it consumes 100% of CPU for the duration of the
call.  This might be an iaxcomm bug, initializing or using libportaudio
wrongly.  

System is Linux 2.6.x (various releases up to 2.6.12.3) with ALSA 
drivers snd_es1968 and snd_ac97_codec loaded as modules, and OSS 
emulation compiled into the kernel.  

This is the same behavior as in recent static builds of iaxcomm
downloadable from the iaxcomm website.  *NB*: The static build 
identified there as "1.0-rc1" does *not* exhibit this problem.

(This might be related to bug #304394, which refers to a possibly similar 
failure in a not-officially-tracked version of libaudio19 that appeared
on debian-mentors.)

Attaching strace to the second thread (as found in /proc/$$/task/)
I see, repeatedly,

  gettimeofday({1123183211, 658005}, NULL) = 0
  ioctl(8, SNDCTL_DSP_GETIPTR, 0xb63caa90) = 0
  read(8, 0x825c268, 160)                 = -1 EINVAL (Invalid argument)
  write(1, "PortAudio: read interrupted!\n", 29) = 29

/proc/$$/fd/8 shows up as /dev/dsp, open for reading.  I don't know
if 0x825c268 here is a legitimate address for the process, but it is 
the only argument that looks like it could be invalid.

I will be happy to try out anything you suggest.

Nathan Myers
[EMAIL PROTECTED]

-- System Information:
Debian Release: 2.2
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12.3+kismet
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages libportaudio0 depends on:
ii  libc6                       2.3.2.ds1-21 GNU C Library: Shared libraries an

libportaudio0 recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to