GNU bug report logs - #11867
24.1.50; Windows bootstrap crash (converting tit files?)

Previous Next

Full log

Message #56 received at 11867 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: rcopley <at> gmail.com, 11867 <at> debbugs.gnu.org
Subject: Re: bug#11867: 24.1.50;
	Windows bootstrap crash (converting tit files?)
Date: Mon, 09 Jul 2012 23:42:02 +0300

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Mon, 9 Jul 2012 19:21:34 +0200
> Cc: rcopley <at> gmail.com, 11867 <at> debbugs.gnu.org
> 
> On Mon, Jul 9, 2012 at 7:14 PM, Eli Zaretskii <eliz <at> gnu.org> wrote:
> 
> > OK.  And how did you attach the debugger?  Or did you run Emacs under
> > the debugger to begin with?
> 
> No. It crashes during the bootstrap (it was a debug bootstrap, with
> --no-opt and --enable-checking, etc), so I did
> 
>   tasklist emacs     ; to get the ID of the only Emacs running
>   cd src
>   gdb -p EMACS-ID
> 

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.

> Emacs is not crashing on w32_abort(), and I don't get a dialog asking
> to attach a debugger.

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?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.