From: Juanma Barranquero <lekktu@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rcopley@gmail.com, 11867@debbugs.gnu.org
Subject: bug#11867: 24.1.50; Windows bootstrap crash (converting tit files?)
Date: Mon, 9 Jul 2012 22:54:22 +0200 [thread overview]
Message-ID: <CAAeL0SQfRnFgcbc8Vx_yHeKoYqGvaCJPhd5L-nEycVtTGBkwvw@mail.gmail.com> (raw)
In-Reply-To: <837gucll9h.fsf@gnu.org>
On Mon, Jul 9, 2012 at 10:42 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> Sorry, I don't understand: how did you know to attach the debugger
> exactly when Emacs crashed or was about to crash? Just attaching a
> debugger stops Emacs wherever it was, which could be anywhere (judging
> by the backtrace, it was in some system call, waiting for some other
> syscall to finish). That place is random, normally having nothing to
> do with the crash.
[...]
> But you said that Emacs crashes while byte-compiling japanese.el.
> When it did crash, did you see the abort dialog, or did you see
> something else?
During the bootstrap, while Emacs is byte-compiling files, it crashes.
I know that because:
1) I get a message from Windows (not the usual w32_abort dialog)
telling me that Emacs has crashed and asking whether I want to send a
report to Microsoft.
2) Bootstrapping stops until I dismiss that message.
At that point, until I tell Windows to dismiss the report sending, I
have all the time in the world to get the id of the only Emacs running
and attach gdb to it.
Additionally,
3) I know that it is in japanese.el, because it happens while
bytecompiling lisp/language/*, and japanese.el is the only missing
.elc afterwards.
I get the crash in all bootstraps, so if you want me to try something, just ask.
Juanma
next prev parent reply other threads:[~2012-07-09 20:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-06 15:55 bug#11867: 24.1.50; Windows bootstrap crash (converting tit files?) Richard Copley
2012-07-06 16:02 ` Eli Zaretskii
2012-07-06 16:12 ` Andreas Schwab
2012-07-06 17:33 ` Eli Zaretskii
2012-07-06 17:39 ` Andreas Schwab
2012-07-06 20:58 ` Richard Copley
2012-07-07 6:31 ` Eli Zaretskii
2012-07-06 16:37 ` Juanma Barranquero
2012-07-06 17:35 ` Eli Zaretskii
2012-07-09 3:56 ` Juanma Barranquero
2012-07-09 16:31 ` Eli Zaretskii
2012-07-09 16:57 ` Juanma Barranquero
2012-07-09 17:09 ` Andreas Schwab
2012-07-09 17:10 ` Juanma Barranquero
2012-07-09 17:14 ` Eli Zaretskii
2012-07-09 17:21 ` Juanma Barranquero
2012-07-09 20:42 ` Eli Zaretskii
2012-07-09 20:54 ` Juanma Barranquero [this message]
2012-07-10 2:43 ` Eli Zaretskii
2012-07-10 11:38 ` Juanma Barranquero
2012-07-10 16:11 ` Eli Zaretskii
2012-07-10 16:36 ` Juanma Barranquero
2012-07-10 17:35 ` Eli Zaretskii
2012-07-10 20:20 ` Juanma Barranquero
2012-07-13 0:19 ` Juanma Barranquero
2012-07-13 4:57 ` Eli Zaretskii
2012-07-13 0:13 ` Juanma Barranquero
2012-07-13 7:57 ` Eli Zaretskii
2012-07-13 8:30 ` Juanma Barranquero
2012-07-13 10:19 ` Eli Zaretskii
2012-07-17 21:35 ` Richard Copley
2012-07-17 23:39 ` Juanma Barranquero
2013-02-18 2:20 ` Glenn Morris
2013-02-18 3:44 ` Eli Zaretskii
[not found] ` <CAPM58og6J2KWsZTAes3E9ZyP=p-oQsW6xwH=5AJMOyTPXU8wYw@mail.gmail.com>
2013-02-18 12:24 ` bug#11867: Fwd: " Richard Copley
2012-07-07 9:09 ` Jason Rumney
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=CAAeL0SQfRnFgcbc8Vx_yHeKoYqGvaCJPhd5L-nEycVtTGBkwvw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=11867@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rcopley@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).