all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>, Ken Brown <kbrown@cornell.edu>
Cc: 17526@debbugs.gnu.org
Subject: bug#17526: 24.3.90; Crash in Cygwin-w32 build
Date: Mon, 19 May 2014 14:00:55 -0700	[thread overview]
Message-ID: <537A7107.8040809@dancol.org> (raw)
In-Reply-To: <83sio5blsx.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 722 bytes --]

On 05/19/2014 12:39 PM, Eli Zaretskii wrote:
>> Date: Mon, 19 May 2014 15:19:24 -0400
>> From: Ken Brown <kbrown@cornell.edu>
>> CC: 17526@debbugs.gnu.org
>>
>> On 5/19/2014 11:18 AM, Eli Zaretskii wrote:
>>>> Date: Mon, 19 May 2014 08:30:49 -0400
>>>> From: Ken Brown <kbrown@cornell.edu>
>>>>
>>>> I just got a crash with the following backtrace:

There goes my BLODA theory (assuming you don't have any). These crashes
(including the indirect-variable one) are all seemingly impossible, but
if there were generalized random memory corruption, I'd expect to see
more severe effects. I have no idea what's wrong. Both trunk and
emacs-24 seem to be affected: did something change in the Cygwin DLL side?


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]

  parent reply	other threads:[~2014-05-19 21:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-19 12:30 bug#17526: 24.3.90; Crash in Cygwin-w32 build Ken Brown
2014-05-19 15:18 ` Eli Zaretskii
2014-05-19 19:19   ` Ken Brown
2014-05-19 19:39     ` Eli Zaretskii
2014-05-19 19:53       ` Ken Brown
2014-05-19 21:00       ` Daniel Colascione [this message]
2014-05-19 21:45         ` Ken Brown
2014-05-19 21:47           ` Daniel Colascione
2014-05-20  1:49             ` Ken Brown
2014-05-20  1:52               ` Daniel Colascione
2014-05-20  2:47           ` Eli Zaretskii
2014-05-21 15:06 ` Eli Zaretskii

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=537A7107.8040809@dancol.org \
    --to=dancol@dancol.org \
    --cc=17526@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=kbrown@cornell.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.