public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Martin Anantharaman" <Martin.Anantharaman@web.de>
To: <cygwin@cygwin.com>
Subject: emacs-w32 24.5.1: Crashes with --daemon and in "About Emacs"
Date: Mon, 18 May 2015 09:42:00 -0000	[thread overview]
Message-ID: <FD353412F4A04A0390C6E2DBC2442E60@MartinsDell> (raw)
In-Reply-To: <55588B3A.8050906@cornell.edu>

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:
$ emacs --daemon -Q
Starting Emacs daemon.

$ emacsclient .shrc
Waiting for Emacs...
*ERROR*: Could not open file: /dev/cons1

$ 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?

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.

Regards, Martin


--
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

  reply	other threads:[~2015-05-18  5:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 11:36 Martin Anantharaman
2015-05-15 17:27 ` Ken Brown
2015-05-17  8:42   ` AW: " Martin Anantharaman
2015-05-18  3:30     ` Ken Brown
2015-05-18  9:42       ` Martin Anantharaman [this message]
2015-05-18 13:43         ` Ken Brown
2015-05-18 14:48           ` Ken Brown
     [not found]           ` <39BFBB82ABFA40A3BBE0531B2CDF2906@MartinsDell>
2015-05-19 12:53             ` AW: " Ken Brown
2015-05-27 12:00               ` Corinna Vinschen

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=FD353412F4A04A0390C6E2DBC2442E60@MartinsDell \
    --to=martin.anantharaman@web.de \
    --cc=cygwin@cygwin.com \
    /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.
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).