(gdb) next
Single stepping until exit from function pthread_cond_wait@@GLIBC_2.3.2,
which has no line number information.
and the processor usage immediately rose to 100% (with CPU fan start). It doesn't seem to make it back from that call, as far as I can see. On the other hand, why should pthread_cond_wait() take up large amounts of CPU time? That seems like a poor implementation. Maybe gdb is confused about what call gnome-cups-icon is actually in because of the above noted stack problems.
Just for kicks I typed:
(gdb) next cond_wait@ @GLIBC_ 2.3.2,
Single stepping until exit from function pthread_
which has no line number information.
and the processor usage immediately rose to 100% (with CPU fan start). It doesn't seem to make it back from that call, as far as I can see. On the other hand, why should pthread_cond_wait() take up large amounts of CPU time? That seems like a poor implementation. Maybe gdb is confused about what call gnome-cups-icon is actually in because of the above noted stack problems.
Any thoughts?
Richard