bug#16737: 24.3.50; Yank causes hang

[Sujith Manoharan]

Dmitry Antipov wrote:
> 1) It's better to attach gdb and try to obtain a backtrace, especially when
> Emacs sits in CPU-eating loops.
> 
> 2) If CPU-eating loop involves I/O (read/write/sendmsg/recvmsg/select/etc.),
> try to understand how the relevant fds are used, by looking under
> /proc/[Emacs PID]/fd directory. (In your log, the most important is fd 4;
> probably this is an X socket).

Ok. The next time this happens, I'll get a gdb backtrace.