From: Andy Moreton <andrewjmoreton@gmail.com>
To: 19380@debbugs.gnu.org
Subject: bug#19380: 24.4.51; Segfault in bootstrap on Windows mingw64
Date: Mon, 15 Dec 2014 14:11:11 +0000 [thread overview]
Message-ID: <vz1egs1ypds.fsf@gmail.com> (raw)
In-Reply-To: <548D7A3C.2050003@gmail.com>
On Sun 14 Dec 2014, Andy Moreton wrote:
> On Sun 14 Dec 2014, Eli Zaretskii wrote:
>
>>> Date: Sun, 14 Dec 2014 11:53:32 +0000
>>> From: Andy Moreton <andrewjmoreton@gmail.com>
>>>
>>> During bootstap from a clean checkout of master, several lisp files
>>> result in a segfault from emacs when they are byte compiled. This seems
>>> to happen with most of the files from lisp/cedet/srecode.
>>>
>>> This is easily reproduced by:
>>> - build emacs from master with mingw64=20
>>> - run "emacs -Q"
>>> - open lisp/cedet/srecode/cpp.el
>>> - Use "Byte compile this file" from the menu.
>>>
> [snipped backtrace etc]
>
>> I suspect aeeaf08 as the culprit. Can you check?
>
> Your suspicions appear to be correct.
>
> Building from a clean checkout, aeeaf08 ("Fixes: debbugs:19161") results
> in a segfault during bootstrap when byte compiling lisp files.
>
> Building from a clean check out of c6f03ed ("Fix a problem in url.el
> without GnuTLS") completes without error.
The changes in e2815bf ("Correct same_at_end when restoring window
points") seems to have fixed this problem.
AndyM
next prev parent reply other threads:[~2014-12-15 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 11:53 bug#19380: 24.4.51; Segfault in bootstrap on Windows mingw64 Andy Moreton
2014-12-14 16:20 ` Eli Zaretskii
2014-12-14 20:54 ` Andy Moreton
2014-12-15 14:11 ` Andy Moreton [this message]
2014-12-16 19:07 ` Glenn Morris
2014-12-16 19:24 ` Glenn Morris
2014-12-16 19:37 ` Ivan Shmakov
2014-12-16 20:39 ` Andy Moreton
2014-12-16 20:59 ` 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
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=vz1egs1ypds.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=19380@debbugs.gnu.org \
/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).