From: Chris Zheng <chriszheng99@gmail.com>
To: eliz@gnu.org
Cc: dmantipov@yandex.ru, emacs-devel@gnu.org
Subject: Re: MS-Windows tester wanted for trunk
Date: Wed, 17 Sep 2014 17:28:00 +0800 [thread overview]
Message-ID: <20140917.172800.824951221171219206.chriszheng99@gmail.com> (raw)
In-Reply-To: <83egvb4n52.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
Subject: Re: MS-Windows tester wanted for trunk
Date: Tue, 16 Sep 2014 18:10:17 +0300
Hi Eli,
> OK. If you continue (e.g., with "make -k"), does it succeed to finish
> the bootstrap, and if so, can you start a session and evaluate the
> problematic code, the one that called 'log', in the scratch buffer?
Thanks for your hints. I have located the crash was coused by
`(ceiling (/ (ceiling (/ (log value) (log 2))) 8.0))' in
/lisp/erc/erc-dcc.el. But I then realized that the bug was more
likely in my system because the simple C code like
double d = 2.00;
d = log (d);
will result in crash. And the crash finally disappeared when I
updated my build system. It seems a bug in the header of MinGW and
has been resolved.
> Also, any idea where did that __fu0_log come from?
Maybe It is generated by GCC.
Wishes,
Chris
next prev parent reply other threads:[~2014-09-17 9:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 8:50 MS-Windows tester wanted for trunk Dmitry Antipov
2014-09-16 13:10 ` Chris Zheng
2014-09-16 14:48 ` Eli Zaretskii
2014-09-16 14:54 ` Chris Zheng
2014-09-16 14:56 ` Chris Zheng
2014-09-16 15:10 ` Eli Zaretskii
2014-09-17 9:28 ` Chris Zheng [this message]
2014-09-17 10:03 ` Eli Zaretskii
2014-09-17 16:56 ` Clang ? [Was: Re: MS-Windows tester wanted for trunk] Dmitry Antipov
2014-09-18 1:05 ` Paul Eggert
2014-09-24 14:45 ` Dmitry Antipov
2014-09-16 14:31 ` MS-Windows tester wanted for trunk Eli Zaretskii
2014-09-16 15:24 ` Dmitry Antipov
2014-09-16 15:58 ` Eli Zaretskii
2014-09-16 20:40 ` Ken Brown
2014-09-16 15:46 ` Dmitry Antipov
2014-09-16 16:03 ` Eli Zaretskii
2014-09-16 14:38 ` 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=20140917.172800.824951221171219206.chriszheng99@gmail.com \
--to=chriszheng99@gmail.com \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).