'Twas brillig, and Pierre-Louis Bossart at 05/08/11 16:24 did gyre and gimble: >> there're multiple pthreads in pulseuadio, which makes reading a bit >> confuse. >> this patch can print each pthread's id. > > Wouldn't it be easier to understand if the thread name was used? We > typically rely on thread names to understand what goes on with > ftrace/pytimechart, I would think this is similar here. I would rather see a > log with "alsa-sink" rather than "PID 6779", it'd also make log comparison > and analysis easier. Yup I agree (in an ideal world we'd name the thread by sink index too... (i.e. "alsa-sink 0") Col -- Colin Guthrie gmane(at)colin.guthr.ie http://colin.guthr.ie/ Day Job: Tribalogic Limited [http://www.tribalogic.net/] Open Source: Mageia Contributor [http://www.mageia.org/] PulseAudio Hacker [http://www.pulseaudio.org/] Trac Hacker [http://trac.edgewall.org/]
