From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: lekktu@gmail.com, eggert@cs.ucla.edu, emacs-devel@gnu.org,
rudalics@gmx.at
Subject: Re: Building master fails on Windows 10 when testing etc/NEWS file
Date: Wed, 18 Sep 2019 21:49:27 +0300 [thread overview]
Message-ID: <83sgottp6w.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ojTzmAgM1zaR=BaXuJeZOHe0SP_APxUyKuM5QBubPsqOA@mail.gmail.com> (message from Richard Copley on Wed, 18 Sep 2019 19:35:31 +0100)
> From: Richard Copley <rcopley@gmail.com>
> Date: Wed, 18 Sep 2019 19:35:31 +0100
> Cc: Juanma Barranquero <lekktu@gmail.com>, Paul Eggert <eggert@cs.ucla.edu>,
> martin rudalics <rudalics@gmx.at>, Emacs Development <emacs-devel@gnu.org>
>
> Thread 1 hit Breakpoint 2, Fload (file=XIL(0x40123a4), noerror=XIL(0), nomessage=XIL(0x30), nosuffix=XIL
> (0), must_suffix=XIL(0x30)) at lread.c:1437
> 1437 report_file_error ("Opening stdio stream", file);
>
> Thread 5 (Thread 19220.0x778):
> #0 0x00007ffd293ceae4 in ntdll!ZwDelayExecution () from C:\WINDOWS\SYSTEM32\ntdll.dll
> #1 0x00007ffd26881e41 in SleepEx () from C:\WINDOWS\System32\KernelBase.dll
> #2 0x00000004003f026e in timer_loop (arg=0x400929120 <real_itimer>) at w32proc.c:473
> #3 0x00007ffd27e55bb4 in KERNEL32!BaseThreadInitThunk () from C:\WINDOWS\System32\kernel32.dll
> #4 0x00007ffd29389ee1 in ntdll!RtlUserThreadStart () from C:\WINDOWS\SYSTEM32\ntdll.dll
> #5 0x0000000000000000 in ?? ()
> Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Thanks, but this is the wrong thread...
Anyway, the problem should be fixed by now, please try the latest
master.
next prev parent reply other threads:[~2019-09-18 18:49 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 7:45 Building master fails on Windows 10 when testing etc/NEWS file martin rudalics
2019-09-18 10:08 ` Paul Eggert
2019-09-18 10:33 ` Richard Copley
2019-09-18 11:26 ` Paul Eggert
2019-09-18 11:36 ` Juanma Barranquero
2019-09-18 12:23 ` Paul Eggert
2019-09-18 12:31 ` Juanma Barranquero
2019-09-18 12:44 ` Eli Zaretskii
2019-09-18 14:27 ` Richard Copley
2019-09-18 15:01 ` Juanma Barranquero
2019-09-18 15:45 ` Eli Zaretskii
2019-09-18 17:00 ` Richard Copley
2019-09-18 17:23 ` Eli Zaretskii
2019-09-18 18:33 ` Eli Zaretskii
2019-09-18 18:35 ` Richard Copley
2019-09-18 18:49 ` Eli Zaretskii [this message]
2019-09-18 18:54 ` Richard Copley
2019-09-18 18:47 ` Eli Zaretskii
2019-09-18 20:16 ` Paul Eggert
2019-09-19 8:18 ` martin rudalics
2019-09-19 9:53 ` Juanma Barranquero
2019-09-19 9:59 ` Juanma Barranquero
2019-09-18 15:05 ` Eli Zaretskii
2019-09-18 12:33 ` Eli Zaretskii
2019-09-18 12:37 ` Eli Zaretskii
2019-09-19 7:27 ` Paul Eggert
2019-09-18 10:35 ` Juanma Barranquero
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=83sgottp6w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
--cc=rcopley@gmail.com \
--cc=rudalics@gmx.at \
/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).