From: "Dhruva Krishnamurthy" <seagull@fastmail.fm>
Cc: bangerth@dealii.org
Subject: Emacs - MinGW32 on W2K
Date: Mon, 24 Feb 2003 21:17:20 +0530 [thread overview]
Message-ID: <20030224154720.803E44E16A@server2.fastmail.fm> (raw)
Hello,
To GCC bug track (person I have CC'ed):
other/9816: GCC 3.2.2 (Mingw Release candidate version) - Regression in
building GNU Emacs 21.3 (CVS)
I did some further testing. I am building GNU Emacs using various
versions of GCC on MinGW32 (W2K) and also MSVC
I have tried GCC 3.2.1, GCC 3.2.2 and GCC 3.3
This happens on both Emacs 21.3 and Emacs 21.2.95
A reproducible recepie for a crash:
- Launch emacs
- Load library "recentf" (load-library "recentf")
- Set the recentf mode (recentf-mode t)
- M-x recentf-open-files
CRASH (Emacs Abort Dialog: A fatal error has occured!)
Next:
- Remove the "lisp/wid-edit.elc" file
- Run the same scenerio, things work
I tried byte-compile-file "lisp/wid-edit.el" to test if a newly generated
".elc" file would work. I does not work.
The above said BUG happens only when I use a GCC compiled Emacs binary
and not with the binary generated through MSVC
I also did the following test to rule out the elisp compilation
regression:
- I built and installed Emacs using MSVC (D:/GNU/emacs-msvc)
- I built and installed Emacs using GCC in a different location
(D:/GNU/emacs-gcc)
- I launched GNU Emacs (GCC compiled binary)
- Opened the "wid-edit.el" file from the MSVC installation
- Byte compiled it
- Launched MSVC emacs and it works just fine.
I seriously doubt the Emacs binary/executable generated by MSVC and GCC
with regards,
dhruva
--
Dhruva Krishnamurthy
Home: http://www32.brinkster.com/schemer/
next reply other threads:[~2003-02-24 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 15:47 Dhruva Krishnamurthy [this message]
2003-02-24 16:03 ` other/9818 (Was: Re: Emacs - MinGW32 on W2K) Wolfgang Bangerth
2003-02-25 18:57 ` Emacs - MinGW32 on W2K Eli Zaretskii
2003-02-26 9:54 ` Dhruva Krishnamurthy
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=20030224154720.803E44E16A@server2.fastmail.fm \
--to=seagull@fastmail.fm \
--cc=bangerth@dealii.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 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.