From: Dan Nicolaescu <dann@ics.uci.edu>
To: Adrian Robert <adrian.b.robert@gmail.com>
Cc: 1107@emacsbugs.donarmstrong.com, William Farrington <wfarr@gatech.edu>
Subject: bug#1107: #1107 - 23.0.60; Emacs --daemon crashes when emacsclient tries to establish a connection on OS X - Emacs bug report logs
Date: Tue, 25 Nov 2008 07:27:03 -0800 (PST) [thread overview]
Message-ID: <200811251527.mAPFR3Bk016272@mothra.ics.uci.edu> (raw)
In-Reply-To: <C9836674-C9AD-44D1-89BF-3E34DBA177DB@gmail.com> (Adrian Robert's message of "Tue, 25 Nov 2008 09:47:03 -0500")
Adrian Robert <adrian.b.robert@gmail.com> writes:
> On Nov 25, 2008, at 1:20 AM, Dan Nicolaescu wrote:
>
> > Adrian Robert <adrian.b.robert@gmail.com> writes:
> >
> >> I just tried to replicate this locally and failed. No crash.
> >> However, it also doesn't work -- emacsclient just always says "can't
> >> find socket; have you started the server?".
> >>
> >> This is new. Emacsclient always worked before, up to and including
> >> multi-tty. Could something in the new daemon support have affected
> >> this? Was there anything in particular that changed as far as how
> >> the
> >> client and server communicate?
> >>
> >> gnuserv, which I use, still works.
> >
> > Can you please clarify, if you are doing
> >
> > emacs --daemon
> >
> > then you can connect with gnuclient, but cannot with emacsclient?
>
> I'm trying emacs -Q/-q/normal --daemon, or "run emacs -Q/-q/normal [no
> opts] + M-x server-start". All give the same result of no socket
> found for emacsclient. If I start emacs (-q/-Q/normal) and do "M-x
> gnuserv-start", then gnuclient works.
> Now I just tried on X11 on Mac, and it works, although there is a
> delay of seconds the first time emacsclient is run before the file
> shows up in emacs.
>
> And, I tried under --enable-cocoa-experimenal-ctrl-g and got the same
> behavior, with these exceptions:
>
> - if there is an emacs window active (no --daemon) the mouse must be
> moved over emacs to get it to pick up the file -- the first time, but
> not subsequent times
>
> - if there is no window active, a crash ensues, sometimes after a
> pause (stack trace below)
>
> Some of this difference must have something to do with how the socket
> event works its way into the input loop, maybe only for the first
> event. If you can summarize what changed in this area with the new
> impl it would help me look into it.
Given that the problem also happens when NOT using --daemon, then the
problem is quite likely not caused by the --daemon changes, the changes
should not affect anything if --daemon is not used.
The daemon code was checked in on 2008-09-21, I'd recommend trying a
version before that date and see if you still have the problem.
You can also try to see if:
emacs -nw -Q --daemon
followed by:
emacsclient -t
also causes problems.
The stack trace posted seems to be taken when using --daemon, one for
emacs -Q -f server-start would be more helpful.
next prev parent reply other threads:[~2008-11-25 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 4:17 bug#1107: #1107 - 23.0.60; Emacs --daemon crashes when emacsclient tries to establish a connection on OS X - Emacs bug report logs Adrian Robert
2008-11-25 6:20 ` Dan Nicolaescu
2008-11-25 14:47 ` Adrian Robert
2008-11-25 15:27 ` Dan Nicolaescu [this message]
2008-11-25 20:08 ` Adrian Robert
2008-11-25 20:34 ` Dan Nicolaescu
2008-11-25 21:15 ` Adrian Robert
2008-11-25 21:24 ` Adrian Robert
-- strict thread matches above, loose matches on Subject: below --
2008-12-10 4:18 Adrian Robert
2008-12-10 6:58 ` Dan Nicolaescu
2008-12-10 15:27 ` Adrian Robert
2008-12-11 16:22 ` Stefan Monnier
2008-12-11 16:21 ` Stefan Monnier
2008-11-25 3:47 Adrian Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200811251527.mAPFR3Bk016272@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=1107@emacsbugs.donarmstrong.com \
--cc=adrian.b.robert@gmail.com \
--cc=wfarr@gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.