public inbox for
help / color / mirror / Atom feed
From: Jon TURNEY <>
Subject: Re: weird xemacs crash
Date: Wed, 18 Feb 2015 13:14:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 17/02/2015 20:35, Eliot Moss wrote:
> Dear Cygwin X --
> I have a situation where cygwin xemacs, both 21.4.23-1 and the newer
> -2 crash when trying to open a file with certain content.  (I copied
> the file; opening it under the other name fails too.)  It's a
> relatively small file, some .c source.  The characters used are all
> reasonable ASCII: newline plus space through 175 octal.  The length
> is 2601 bytes.
> Here is the stackdump:
> Stack trace:
> Frame     Function  Args
> 002899C4  61030F12 (000002E0, 0000EA60, 000000A4, 00289A24)
> 00289AE4  610E468A (6119EE10, 00000000, 00289B18, 00000000)
> What's the next step?

Assuming I have the same cygwin DLL as you...

> $ cat stackdump | awk '/^[0-9]/{print $2}' | addr2line -asf -e /usr/lib/debug/usr/bin/cygwin1.dbg | paste - - - | column -t
> 0x61030f12  _ZN7_cygtls19call_signal_handlerEv@4
> 0x610e468a  _Z8sig_sendP6_pinfoR9siginfo_tP7_cygtls@12

But are you sure this isn't the problem mentioned in [1]?


Volunteer Cygwin/X X Server maintainer

Unsubscribe info:
Problem reports:

  reply	other threads:[~2015-02-18 13:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 20:35 Eliot Moss
2015-02-18 13:14 ` Jon TURNEY [this message]
2015-02-18 14:09   ` Eliot Moss

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).