bug#17847: 24.3; Emacsclient hang/crash

[Robert Horn <rjhorn@alum.mit.edu>]

Eli Zaretskii writes:

>> From: Robert Horn <rjhorn@alum.mit.edu>
>> Date: Wed, 25 Jun 2014 11:32:19 -0400
>> 
>> Minimal test:
>> 
>> 1. Start emacs --daemon -Q -s test
>> 2. Start emacsclient --alternate-editor="" -c -s test
>> 3. Exit emacsclient with c-X 5 0
>> 4. Repeat 2. and 3. until fail (3-6 tries typically)
>> 
>> Failure is a momentary appearance of the X-window frame for the
>> emacsclient.  After it is gone, the emacs daemon has also exited.  
>> 
>> Related test:
>> 1. Start emacs --daemon -s test   (full startup with configuration
>> indicated below).
>> 2., 3., 4. the same
>
> What's the significance of all the non-default options in this recipe?
> Does the problem only happen if you use precisely those options?  If
> so, can you tell why you need them?

I retested the minimal with starting emacs using "emacs --daemon -Q"
and emacsclient using "emacsclient -c".  The results are the same.
After 5 cycles there is the momentary appearence of the X-window frame,
then both emacs and emacsclient processes have exited.

They were in there as leftovers from my old setup where I want
emacsclient to go to a particular socket and start emacs automatically
if there is not a daemon running already.

R Horn