X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=kBfYaRrMtlmyR5Xgq4eB5inaUWzIz0S9cK3c/rE/zBa
	EswpOr+aFtd2PELItc7A6HJ7ddRibxrFEX5YOChk0bQ9+AoCVjJ+rowrFqSb0ZKW
	MKDml+0x+Vl+ibVlikgsjh8nv1er97Jkq7OEAOLcLCXkBTBT/rBGK+4BkJuHQZTE
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=ALgiM9efpRHP/k6dvth1gZR/M4E=; b=bmqn4p7BzamlVkuLZ
	yjOJjjfN82Zz3sq8wMbZmVNMEdVwulhlEku8T/OD/LTgNs+wTxRoGrqXU1LY9D2t
	ohsJHPm5fZ7jLz68mqJOdbLtIssXOF/YHeVBd2NGuCBNPoqvMfGoSfj/xHJ0p8h6
	HLFy49F6JFjXVzvYwLyBt555+w=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.8 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS,T_RP_MATCHES_RCVD autolearn=ham version=3.3.2
X-HELO:	limerock02.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<5559EC69.2000704@cornell.edu>
Date:	Mon, 18 May 2015 09:43:05 -0400
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
References:	<55588B3A DOT 8050906 AT cornell DOT edu> <FD353412F4A04A0390C6E2DBC2442E60 AT MartinsDell> <5559DC54 DOT 8050008 AT cornell DOT edu>
In-Reply-To:	<5559DC54.8050008@cornell.edu>
X-IsSubscribed:	yes

On 5/18/2015 8:34 AM, Ken Brown wrote:
> On 5/18/2015 1:57 AM, Martin Anantharaman wrote:
>> Ken,
>>
>> so that we do not get side-tracke by differences in our emacs-customizations
>> I now re-produced the error in a "clean" environment, i.e. I unset
>> ALTERNATE_EDITOR and did the following:
>
> Did you also make sure that EMACS_SERVER_FILE was not set?
>
>> $ emacs --daemon -Q
>> Starting Emacs daemon.
>>
>> $ emacsclient .shrc
>> Waiting for Emacs...
>> *ERROR*: Could not open file: /dev/cons1
>
> So this time emacsclient did not complain that it couldn't find the socket.  But
> why is it trying to open /dev/cons1?  Are you running these commands in a
> Windows console rather than a Cygwin Terminal (mintty)?  If so, please try it in
> a Cygwin Terminal.
>
>> $ emacsclient .shrc
>> Waiting for Emacs...
>>
>> (emacsclient returns immediately, task-manager shows there is no more
>> emacs-w32 process and there is a new stackdump in the working directory)
>>
>> $ cat emacs-w32.exe.stackdump
>> Stack trace:
>> Frame     Function  Args
>> 017075E4  61033210 (00000558, 0000EA60, 000000A4, 01707654)
>> 01707714  610EF12F (00000012, 00000000, 0170776C, 6110E4AF)
>>
>> To get some more insight I tried to do the same on another machine running
>> Arch Linux (though with emacs 24.3 under LXDE) and guess what: At any number
>> of calls to emacsclient as above a (emacs-)window is opened in the TERMINAL
>> from which I run emacsclient (though a new desktop-window is opened when
>> emacsclient is called with the -c option) - which is not working in my
>> Cygwin/Windows combination giving the error "*ERROR*: Could not open file:
>> /dev/cons1" and crashing emacs on the next c.
>>
>> So what happends when you call emacs and then emacsclient in the same order
>> as shown?
>
> I get the Linux behavior that you just described.
>
>> Regarding the 2. problem (crash on About Emacs) it happens exactly the same
>> way when I call emacs with emacs -Q and immediately open About Emacs. I will
>> get the debuginfo and try to see where/why it is crashing when I have a
>> little spare time - I was just hoping that the stackdump I had attached
>> before might actually allow you to localize the error.
>
> The two addresses shown in the stackdump (in the "Function" column) are both in
> cygwin1.dll.
>
> $ addr2line -e /usr/lib/debug/usr/bin/cygwin1.dbg 61033210
> /usr/src/debug/cygwin-2.0.2-1/winsup/cygwin/exceptions.cc:1540
>
> $ addr2line -e /usr/lib/debug/usr/bin/cygwin1.dbg 610EF12F
> /usr/src/debug/cygwin-2.0.2-1/winsup/cygwin/sigproc.cc:714
>
> This doesn't tell us anything about what was happening in emacs.

And here too I recommend starting emacs from a Cygwin Terminal if that isn't 
what you've been doing.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -