public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/9818 (Was: Emacs - MinGW32 on W2K (fwd))
Date: Mon, 24 Feb 2003 16:06:00 -0000	[thread overview]
Message-ID: <20030224160600.12219.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/9818; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: other/9818 (Was: Emacs - MinGW32 on W2K (fwd))
Date: Mon, 24 Feb 2003 09:56:15 -0600 (CST)

 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 
 ---------- Forwarded message ----------
 Date: Mon, 24 Feb 2003 21:17:20 +0530
 From: Dhruva Krishnamurthy <seagull@fastmail.fm>
 To: Emacs Devel <emacs-devel@gnu.org>
 Cc: bangerth@dealii.org, Emacs Bug <emacs-pretest-bug@gnu.org>
 Subject: Emacs - MinGW32 on W2K
 
 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/
 


                 reply	other threads:[~2003-02-24 16:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20030224160600.12219.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.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.
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).