GNU bug report logs - #13062
24.3.50; emacs_backtrace.txt

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 13062 in the body.
You can then email your comments to 13062 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

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

From: "Drew Adams" <drew.adams <at> oracle.com>
To: <bug-gnu-emacs <at> gnu.org>
Subject: 24.3.50; emacs_backtrace.txt
Date: Sun, 2 Dec 2012 11:49:52 -0800

Backtrace:
0x0115459C
0x0115460E
0x01001459
0x01021B9F
0x012065C7
0x012030A6
0x0103B7F6
0x0104F409
0x01038B18
0x01010F1D
0x010382AB
0x0101097A
0x01038265
0x0103781F
0x01037B4C
0x010029AB
0x010010F9
0x7C817073
 
 
 
In GNU Emacs 24.3.50.1 (i386-mingw-nt5.1.2600)
 of 2012-11-19 on MS-W7-DANI
Bzr revision: 110950 monnier <at> iro.umontreal.ca-20121119182725-5p6w4wjimm7epggr
Windowing system distributor `Microsoft Corp.', version 5.1.2600
Configured using:
 `configure --with-gcc (4.7) --no-opt --enable-checking --cflags
 -Ic:/emacs/libs/libXpm-3.5.10/include -Ic:/emacs/libs/libXpm-3.5.10/src
 -Ic:/emacs/libs/libpng-1.2.37-lib/include -Ic:/emacs/libs/zlib-1.2.5
 -Ic:/emacs/libs/giflib-4.1.4-1-lib/include
 -Ic:/emacs/libs/jpeg-6b-4-lib/include
 -Ic:/emacs/libs/tiff-3.8.2-1-lib/include
 -Ic:/emacs/libs/libxml2-2.7.8-w32-bin/include/libxml2
 -Ic:/emacs/libs/gnutls-3.0.9-w32-bin/include
 -Ic:/emacs/libs/libiconv-1.9.2-1-lib/include'
 

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 13062 <at> debbugs.gnu.org
Subject: Re: bug#13062: 24.3.50; emacs_backtrace.txt
Date: Sun, 02 Dec 2012 22:33:05 +0200

> From: "Drew Adams" <drew.adams <at> oracle.com>
> Date: Sun, 2 Dec 2012 11:49:52 -0800
> 
> 
> Backtrace:
> 0x0115459C
> 0x0115460E
> 0x01001459
> 0x01021B9F
> 0x012065C7
> 0x012030A6
> 0x0103B7F6
> 0x0104F409
> 0x01038B18
> 0x01010F1D
> 0x010382AB
> 0x0101097A
> 0x01038265
> 0x0103781F
> 0x01037B4C
> 0x010029AB
> 0x010010F9
> 0x7C817073

Translation:

  w32_backtrace at C:\emacs\trunk\src/w32fns.c:7735
  emacs_abort at C:\emacs\trunk\src/w32fns.c:7767
  terminate_due_to_signal at C:\emacs\trunk\src/emacs.c:341
  die at C:\emacs\trunk\src/alloc.c:6491
  redisplay_internal at C:\emacs\trunk\src/xdisp.c:13529
  redisplay at C:\emacs\trunk\src/xdisp.c:12683
  read_char at C:\emacs\trunk\src/keyboard.c:2428
  read_key_sequence at C:\emacs\trunk\src/keyboard.c:9230
  command_loop_1 at C:\emacs\trunk\src/keyboard.c:1458
  internal_condition_case at C:\emacs\trunk\src/eval.c:1288
  command_loop_2 at C:\emacs\trunk\src/keyboard.c:1167
  internal_catch at C:\emacs\trunk\src/eval.c:1059
  command_loop at C:\emacs\trunk\src/keyboard.c:1146
  recursive_edit_1 at C:\emacs\trunk\src/keyboard.c:778
  Frecursive_edit at C:\emacs\trunk\src/keyboard.c:842
  main at C:\emacs\trunk\src/emacs.c:1560
  ?? at crt1.c:0

It's an assertion violation here:

      if (!EQ (old_frame, selected_frame)
	  && FRAME_LIVE_P (XFRAME (old_frame)))
	/* We played a bit fast-and-loose above and allowed selected_frame
	   and selected_window to be temporarily out-of-sync but let's make
	   sure this stays contained.  */
	select_frame_for_redisplay (old_frame);
      eassert (EQ (XFRAME (selected_frame)->selected_window,  <<<<<<<<<<<
		   selected_window));

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

From: Glenn Morris <rgm <at> gnu.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 13062 <at> debbugs.gnu.org
Subject: Re: bug#13062: 24.3.50; emacs_backtrace.txt
Date: Fri, 22 Feb 2013 20:07:12 -0500

Eli Zaretskii wrote:

> It's an assertion violation here:
>
>       if (!EQ (old_frame, selected_frame)
> 	  && FRAME_LIVE_P (XFRAME (old_frame)))
> 	/* We played a bit fast-and-loose above and allowed selected_frame
> 	   and selected_window to be temporarily out-of-sync but let's make
> 	   sure this stays contained.  */
> 	select_frame_for_redisplay (old_frame);
>       eassert (EQ (XFRAME (selected_frame)->selected_window,  <<<<<<<<<<<
> 		   selected_window));

So can anything be done with this information?

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: 13062 <at> debbugs.gnu.org
Subject: Re: bug#13062: 24.3.50; emacs_backtrace.txt
Date: Sat, 23 Feb 2013 12:22:04 +0200

> From: Glenn Morris <rgm <at> gnu.org>
> Cc: 13062 <at> debbugs.gnu.org
> Date: Fri, 22 Feb 2013 20:07:12 -0500
> 
> Eli Zaretskii wrote:
> 
> > It's an assertion violation here:
> >
> >       if (!EQ (old_frame, selected_frame)
> > 	  && FRAME_LIVE_P (XFRAME (old_frame)))
> > 	/* We played a bit fast-and-loose above and allowed selected_frame
> > 	   and selected_window to be temporarily out-of-sync but let's make
> > 	   sure this stays contained.  */
> > 	select_frame_for_redisplay (old_frame);
> >       eassert (EQ (XFRAME (selected_frame)->selected_window,  <<<<<<<<<<<
> > 		   selected_window));
> 
> So can anything be done with this information?

I think this should be closed, as there were massive changes in this
area (on the trunk) with the purpose of avoiding those assertion
violations.

Message #19 received at 13062-done <at> debbugs.gnu.org (full text, mbox):

From: Glenn Morris <rgm <at> gnu.org>
To: 13062-done <at> debbugs.gnu.org
Subject: Re: bug#13062: 24.3.50; emacs_backtrace.txt
Date: Sat, 23 Feb 2013 14:02:03 -0500

Eli Zaretskii wrote:

> I think this should be closed, as there were massive changes in this
> area (on the trunk) with the purpose of avoiding those assertion
> violations.

OK

PS IIUC These binaries are intended for non-technical users (who can't
build Emacs). Is it useful for them to be compiled with assertion
checking? It just seems to lead to lots of crashes that the users
can't diagnose.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Glenn Morris <rgm <at> gnu.org>
Cc: rgm <at> gnu.org, drew.adams <at> oracle.com, 13062 <at> debbugs.gnu.org
Subject: Re: bug#13062: 24.3.50; emacs_backtrace.txt
Date: Sat, 23 Feb 2013 22:10:36 +0200

> From: Glenn Morris <rgm <at> gnu.org>
> Date: Sat, 23 Feb 2013 14:02:03 -0500
> 
> PS IIUC These binaries are intended for non-technical users (who can't
> build Emacs). Is it useful for them to be compiled with assertion
> checking? It just seems to lead to lots of crashes that the users
> can't diagnose.

I think assertions help _us_ diagnose problems, because they trigger
earlier than a crash that follows, and pinpoint the root cause better.

Previous Next

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