unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10092@debbugs.gnu.org
Subject: bug#10092: 24.0.91; `C-g' makes Emacs to crash
Date: Fri, 25 Nov 2011 00:51:04 +0100	[thread overview]
Message-ID: <CAAeL0SSPzYVZzuLTzix7EkAWGf9AqvVS+UZPHfEhaGQ96Okimw@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0iLx9Com9ooT2wOeh8W+gw0xxYTWH5aM4qqNxg3G_gYGg@mail.gmail.com>

> * gcc version 4.6.1
> * mingw-get version 0.4-alpha-1

When building with optimizations, are you passing the
-fno-omit-frame-pointer flag to GCC?

There was a discussion in emacs-devel about one month ago. Eli said:

   This thread:

    http://lists.gnu.org/archive/html/qemu-devel/2011-10/msg01697.html

   suggests that it probably is.  IIUC, there's an issue with setjmp in
   the MS runtime not working when -fomit-frame-pointer is used, and the
   MinGW GCC 4.6.1 turns on -fomit-frame-pointer by default when
   optimizing.  Since Emacs uses setjmp/longjmp _a_lot_, and in
   particular C-g throws to the top level via this mechanism, it seems
   like we have a smoking gun.

   Perhaps rebuild Emacs with -fno-omit-frame-pointer, and see if that
   helps.


    Juanma





  reply	other threads:[~2011-11-24 23:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  9:20 bug#10092: 24.0.91; `C-g' makes Emacs to crash Dani Moncayo
2011-11-21 10:26 ` Dani Moncayo
2011-11-21 17:07   ` Eli Zaretskii
2011-11-21 17:59     ` Dani Moncayo
2011-11-23 22:11 ` Dani Moncayo
2011-11-24  3:47   ` Eli Zaretskii
2011-11-24 19:24     ` Dani Moncayo
2011-11-24 19:39       ` Dani Moncayo
2011-11-24 20:46         ` Juanma Barranquero
2011-11-24 21:26           ` Dani Moncayo
2011-11-24 22:38             ` Juanma Barranquero
2011-11-24 23:32               ` Dani Moncayo
2011-11-24 23:51                 ` Juanma Barranquero [this message]
2011-11-25  8:14                 ` Eli Zaretskii
2011-11-25 16:03                   ` Dani Moncayo
2011-11-25 18:15                     ` 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=CAAeL0SSPzYVZzuLTzix7EkAWGf9AqvVS+UZPHfEhaGQ96Okimw@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=10092@debbugs.gnu.org \
    --cc=dmoncayo@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 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).