From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Corrupt Cygwin64 install?
Date: Wed, 21 Sep 2016 22:09:00 -0000 [thread overview]
Message-ID: <af1fbd86-ab87-0cbb-d1b2-a2f8b993637a@cornell.edu> (raw)
In-Reply-To: <CACt7iw=dixzLm_uu7H5Lc2FpjBSmFzjjGt=ryPr9FN0sanD+Og@mail.gmail.com>
On 9/21/2016 5:14 PM, Mike McCarty wrote:
> I have cygwin64 installed and up until recently, everything was
> working fine. However, I updated a while back and now I notice that
> emacs doesn't run:
>
> $ which emacs
> /usr/bin/emacs
> $ emacs
> $ emacs --version
> GNU Emacs 25.1.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> GNU Emacs comes with ABSOLUTELY NO WARRANTY.
> You may redistribute copies of GNU Emacs
> under the terms of the GNU General Public License.
> For more information about these matters, see the file named COPYING.
> $ emacs a.txt
>
> It doesn't really crash, it just returns immediately. So I thought I'd
> see what strace reported...
>
> $ strace /usr/bin/emacs
> 0 [main] strace 5196 D:\cygwin64\bin\strace.exe: *** fatal error
> - Internal error: TP_NUM_W_BUFS too small: 50.
> 614 [main] strace 5196 cygwin_exception::open_stackdumpfile:
> Dumping stack trace to strace.exe.stackdump
You can't run strace on a symlink. Try 'strace /usr/bin/emacs-w32.exe'
(or whichever emacs binary the symlink resolves to).
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
next prev parent reply other threads:[~2016-09-21 22:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 22:04 Mike McCarty
2016-09-21 22:09 ` Ken Brown [this message]
2016-09-21 22:35 Mike McCarty
2016-09-22 14:18 ` Ken Brown
2016-09-26 21:09 ` Mike McCarty
2016-09-27 2:00 ` Ken Brown
2016-09-27 2:18 ` Brian Inglis
2016-09-27 15:05 ` Mike McCarty
2016-09-27 17:59 ` Achim Gratz
2016-09-27 18:06 ` Mike McCarty
2016-09-27 18:12 ` Achim Gratz
2016-09-27 18:29 ` Achim Gratz
2016-09-27 20:15 ` Mike McCarty
2016-09-28 0:06 ` Brian Inglis
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=af1fbd86-ab87-0cbb-d1b2-a2f8b993637a@cornell.edu \
--to=kbrown@cornell.edu \
--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).