From: Ken Brown <kbrown@cornell.edu>
To: Stefan Kangas <stefan@marxist.se>,
Jon TURNEY <jon.turney@dronecode.org.uk>
Cc: 18769-done@debbugs.gnu.org
Subject: bug#18769: 24.4; assertion failed in emacs-24.4 on cygwin x86_64
Date: Wed, 12 Aug 2020 13:31:25 -0400 [thread overview]
Message-ID: <e44bf72a-d40a-d7e3-c9cc-4b8339d7be3b@cornell.edu> (raw)
In-Reply-To: <CADwFkmm5zuopC+EZV4o3ERwABaNZ43bnNHoiKCTr8gVcV8i2hw@mail.gmail.com>
On 8/12/2020 1:06 PM, Stefan Kangas wrote:
> Jon TURNEY <jon.turney@dronecode.org.uk> writes:
>
>> On 19/10/2014 20:18, Ken Brown wrote:
>>> On 10/19/2014 2:54 PM, Ken Brown wrote:
>>>> On 10/19/2014 1:47 PM, Eli Zaretskii wrote:
>>>>> Could be one more of those unexplained assertion violations, see bug
>>>>> #18438. And if that's so, then the problem isn't limited to the
>>>>> Cygwin-w32 builds.
>>>>
>>>> Right. So I can stop wasting my time (and yours) by looking for
>>>> something
>>>> specific to that build. But the problem does seem limited to 64-bit
>>>> Cygwin, FWIW.
>>>
>>> Jon, have you by any chance tried the latest Cygwin snapshot to see if
>>> that makes a difference? I think there have been major changes in
>>> exception handling (64 bit only), which may or may not be relevant.
>>
>> I've been trying with the 20141017 snapshot and your emacs-24.4-0 build for the
>> past couple of days, but unfortunately I still get 'impossible' asserts.
>
> That was almost 6 years ago. Are you still seeing this on a recent
> version of Emacs, such as the recently released version 27.1?
No, this was fixed long ago. Closing.
Ken
prev parent reply other threads:[~2020-08-12 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 15:37 bug#18769: 24.4; assertion failed in emacs-24.4 on cygwin x86_64 Jon TURNEY
2014-10-19 17:47 ` Eli Zaretskii
2014-10-19 18:54 ` Ken Brown
2014-10-19 19:04 ` Eli Zaretskii
2014-10-20 20:46 ` Ken Brown
2014-10-19 19:18 ` Ken Brown
2014-10-23 11:22 ` Jon TURNEY
2020-08-12 17:06 ` Stefan Kangas
2020-08-12 17:31 ` Ken Brown [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e44bf72a-d40a-d7e3-c9cc-4b8339d7be3b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=18769-done@debbugs.gnu.org \
--cc=jon.turney@dronecode.org.uk \
--cc=stefan@marxist.se \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).