From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17510@debbugs.gnu.org, dmantipov@yandex.ru
Subject: bug#17510: 24.3.91; Problem with `emacs --daemon' in cygw32 build
Date: Sun, 18 May 2014 10:30:28 -0400 [thread overview]
Message-ID: <5378C404.8050405@cornell.edu> (raw)
In-Reply-To: <831tvremfz.fsf@gnu.org>
On 5/18/2014 12:32 AM, Eli Zaretskii wrote:
> Thanks, but you need to be more selective: which one of these changes
> is the root cause, and why?
It's not easy to be selective; these aren't independent changes. There
used to be a `w32_display_name_list', which Dmitry removed. Along with
this change, he removed the code that used to be in x_delete_display (to
delete a display from the list) and replaced it by a FIXME.
> In general, everything that is related to one_w32_display_info is
> specific to the WINDOWSNT port, so perhaps the problem is that the
> Cygwin-w32 build is incorrectly treated the same. But where exactly?
Looking at the code, I don't see why this problem is specific to the
Cygwin-w32 build. Can you reproduce it in the Windows build?
I *think* what must be happening in the recipe that I gave for this bug
is that every time a client frame is closed, x_delete_display is called.
Before Dmitry's change, this would actually delete something from a
list. Now it doesn't, and the server gets messed up and ultimately dies
on the third attempt to create a client frame.
Unless there's an obvious fix for this, it seems to me that we're far
enough into the pretest that we should just revert to the old code, at
least for emacs-24.
Ken
next prev parent reply other threads:[~2014-05-18 14:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 17:50 bug#17510: 24.3.91; Problem with `emacs --daemon' in cygw32 build Ken Brown
2014-05-16 20:06 ` Ken Brown
2014-05-17 23:39 ` Ken Brown
2014-05-18 4:32 ` Eli Zaretskii
2014-05-18 14:30 ` Ken Brown [this message]
2014-05-18 15:11 ` Eli Zaretskii
2014-05-18 19:36 ` Ken Brown
2014-05-19 12:03 ` Ken Brown
2014-05-19 16:46 ` Eli Zaretskii
2014-05-19 17:31 ` Eli Zaretskii
2014-05-19 19:25 ` Ken Brown
2014-05-24 12:38 ` Ken Brown
2014-05-24 12:59 ` Eli Zaretskii
2014-05-24 18:14 ` Ken Brown
2014-05-24 22:18 ` Ken Brown
2014-05-24 19:28 ` Daniel Colascione
2014-05-24 22:18 ` Ken Brown
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5378C404.8050405@cornell.edu \
--to=kbrown@cornell.edu \
--cc=17510@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).