On Mon, 19.01.09 21:38, Aleksander Kamenik (aleksan...@krediidiinfo.ee) wrote:
> > Lennart Poettering wrote: > > > This really looks like some ALSA issue. I fear they only way to figure > > out what is going on is using gdb and stepping through > > pa_alsa_set_hw_params(). Do you think you can do this? > > I've player around with gdb in the past, though don't remember much. In > the worst case I'll learn something :). > > IIRC with Fedora I have to get a -debug package of pulseaudio first to > get the debug symbols? I can't find it though. debuginfo-install pulseaudio LD_BIND_NOW=1 gdb /usr/bin/pulseaudio b pa_alsa_set_hw_params r And then use "n" to step though the code to check which call in pa_alsa_set_hw_params() actually fails. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
