From: Dani Moncayo <dmoncayo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10092@debbugs.gnu.org
Subject: bug#10092: 24.0.91; `C-g' makes Emacs to crash
Date: Thu, 24 Nov 2011 20:39:53 +0100 [thread overview]
Message-ID: <CAH8Pv0gj2QCkTKiONY1wt_Vypvja29VecASZTh7szgMSkuzVjQ@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0h9MQqu5WR7zp6QcpemQb8jPFkpAYuAgpzXXsCaZuaG=Q@mail.gmail.com>
>>> For the record: I still experience this problem on MS-Windows XP
>>> systems, when I take there my binary distribution, made on a
>>> MS-Windows 7 64-bit system (with the latest mingw, updated a few days
>>> ago).
>>
>> Please run Emacs under GDB and post the backtrace.
>
> I've never done such thing. Is the procedure documented somewhere?
Ok, I've found a description in "nt/INSTALL".
Here's the backtrace:
----------------------------------------------------
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 140.0x90]
0x77c3554a in msvcrt!_abnormal_termination ()
from C:\WINDOWS\system32\msvcrt.dll
(gdb) bt
#0 0x77c3554a in msvcrt!_abnormal_termination ()
from C:\WINDOWS\system32\msvcrt.dll
#1 0x77c39bc6 in strerror () from C:\WINDOWS\system32\msvcrt.dll
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)
----------------------------------------------------
--
Dani Moncayo
next prev parent reply other threads:[~2011-11-24 19:39 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 [this message]
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
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=CAH8Pv0gj2QCkTKiONY1wt_Vypvja29VecASZTh7szgMSkuzVjQ@mail.gmail.com \
--to=dmoncayo@gmail.com \
--cc=10092@debbugs.gnu.org \
--cc=eliz@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).