bug#8272: Follow up

[Stefan Kangas]

Andrew Myers <asm198@gmail.com> writes:

> It appears that this was caused by a patch to the Allegro elisp files made by 
> one of our developers.  I attached to the Allegro lisp process with gdb and 
> saw that it was also hung on __select_nocancel().
> The patch to elisp removed an initialization message from emacs to the alisp 
> subprocess.  My best guess right now is that this meant Allegro caught a 
> message meant for emacs through an inherited file descriptor.  Is this 
> possible?
> Thanks,
> Andrew Myers

This bug report unfortunately never got a reply 8 years ago.

It seems like this was not a bug in Emacs, since you write above that
it was caused by an external patch.  I'm therefore closing this bug.

If you believe this is wrong and this is still an issue, please reopen
the bug report.

Best regards,
Stefan Kangas