[pulseaudio-discuss] On SHM related Bus errors
Colin Guthrie
gmane at colin.guthr.ie
Sun May 9 01:28:19 PDT 2010
Hi,
There has been some discussion about bus errors and SHM of late.
I've just seen my first bug report on the topic!
https://bugs.kde.org/show_bug.cgi?id=236524
Extract (5 is the lowest number in the call stack due to the crash handler)
Application: KNotify (knotify4), signal: Bus error
[KCrash Handler]
#5 0x00007f071225df5e in pa_shm_create_rw () from
/usr/lib64/libpulsecommon-0.9.21.so
#6 0x00007f0712252676 in pa_mempool_new () from
/usr/lib64/libpulsecommon-0.9.21.so
#7 0x00007f07152a8958 in pa_context_new_with_proplist () from
/usr/lib64/libpulse.so.0
#8 0x00007f0718c33d08 in Phonon::PulseSupport::PulseSupport
(this=0x6de530) at
/usr/src/debug/phonon-4.4/phonon/pulsesupport.cpp:712
This happens after a resume from suspend.
What kind of thing can cause this? Non writable SHM area? Full up?
What is the best way to go about debugging this?
Col
--
Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/
Day Job:
Tribalogic Limited [http://www.tribalogic.net/]
Open Source:
Mandriva Linux Contributor [http://www.mandriva.com/]
PulseAudio Hacker [http://www.pulseaudio.org/]
Trac Hacker [http://trac.edgewall.org/]
More information about the pulseaudio-discuss
mailing list