From: Christoph Scholtes <cschol2112@googlemail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-emacs-windows@gnu.org, Leo <sdl.web@gmail.com>, emacs-devel@gnu.org
Subject: Re: emacs-20111024-r106182 Windows Binaries
Date: Tue, 25 Oct 2011 06:32:41 -0600 [thread overview]
Message-ID: <86sjmhmety.fsf@googlemail.com> (raw)
In-Reply-To: <E1RIcnp-0003A0-Bw@fencepost.gnu.org> (Eli Zaretskii's message of "Tue, 25 Oct 2011 04:56:09 -0400")
Eli Zaretskii <eliz@gnu.org> writes:
>> <EventData>
>> <Data>emacs.exe</Data>
>> <Data>24.0.90.0</Data>
>> <Data>4e9e1382</Data>
>> <Data>ntdll.dll</Data>
>> <Data>6.1.7601.17514</Data>
>> <Data>4ce7ba58</Data>
>> <Data>c0000029</Data>
>> <Data>000907b6</Data>
>> <Data>760</Data>
>> <Data>01cc91fd0016c7e4</Data>
>> <Data>D:\emacs-24.0.90\bin\emacs.exe</Data>
>> <Data>C:\windows\SysWOW64\ntdll.dll</Data>
>
> Yes, that's the same crash that I cited.
Leo said that this happens with the last weekly build I provided. It was
compiled _without_ optimizations. The original report claimed to compile
with `-O2'.
Just to make sure, is specifying `--no-opt' enough to disable
optimizations when configuring or do I have to specify `-O0'
explicitely?
If this turns out to be a problem with 4.6.1 in general, I will switch
back to an older version. Or should I use `-fno-omit-frame-pointer'?
Christoph
next prev parent reply other threads:[~2011-10-25 12:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 3:56 emacs-20111024-r106182 Windows Binaries Christoph Scholtes
2011-10-25 5:19 ` Leo
2011-10-25 5:27 ` Christoph Scholtes
2011-10-25 5:46 ` Leo
2011-10-25 8:00 ` Eli Zaretskii
2011-10-25 8:36 ` Leo
2011-10-25 8:56 ` Eli Zaretskii
2011-10-25 9:14 ` Leo
2011-10-25 12:32 ` Christoph Scholtes [this message]
2011-10-25 13:12 ` Eli Zaretskii
2011-10-26 1:06 ` Christoph Scholtes
2011-10-26 8:12 ` Eli Zaretskii
2011-10-26 3:25 ` Leo
2011-10-26 8:37 ` [h-e-w] " 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=86sjmhmety.fsf@googlemail.com \
--to=cschol2112@googlemail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=help-emacs-windows@gnu.org \
--cc=sdl.web@gmail.com \
/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.