* bug#13062: 24.3.50; emacs_backtrace.txt
@ 2012-12-02 19:49 Drew Adams
2012-12-02 20:33 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Drew Adams @ 2012-12-02 19:49 UTC (permalink / raw)
To: 13062
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@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'
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#13062: 24.3.50; emacs_backtrace.txt
2012-12-02 19:49 bug#13062: 24.3.50; emacs_backtrace.txt Drew Adams
@ 2012-12-02 20:33 ` Eli Zaretskii
2013-02-23 1:07 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2012-12-02 20:33 UTC (permalink / raw)
To: Drew Adams; +Cc: 13062
> From: "Drew Adams" <drew.adams@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));
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#13062: 24.3.50; emacs_backtrace.txt
2012-12-02 20:33 ` Eli Zaretskii
@ 2013-02-23 1:07 ` Glenn Morris
2013-02-23 10:22 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2013-02-23 1:07 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 13062
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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#13062: 24.3.50; emacs_backtrace.txt
2013-02-23 1:07 ` Glenn Morris
@ 2013-02-23 10:22 ` Eli Zaretskii
2013-02-23 19:02 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Eli Zaretskii @ 2013-02-23 10:22 UTC (permalink / raw)
To: Glenn Morris; +Cc: 13062
> From: Glenn Morris <rgm@gnu.org>
> Cc: 13062@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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#13062: 24.3.50; emacs_backtrace.txt
2013-02-23 10:22 ` Eli Zaretskii
@ 2013-02-23 19:02 ` Glenn Morris
2013-02-23 20:10 ` Eli Zaretskii
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2013-02-23 19:02 UTC (permalink / raw)
To: 13062-done
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#13062: 24.3.50; emacs_backtrace.txt
2013-02-23 19:02 ` Glenn Morris
@ 2013-02-23 20:10 ` Eli Zaretskii
0 siblings, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2013-02-23 20:10 UTC (permalink / raw)
To: Glenn Morris; +Cc: 13062
> From: Glenn Morris <rgm@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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-02-23 20:10 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-02 19:49 bug#13062: 24.3.50; emacs_backtrace.txt Drew Adams
2012-12-02 20:33 ` Eli Zaretskii
2013-02-23 1:07 ` Glenn Morris
2013-02-23 10:22 ` Eli Zaretskii
2013-02-23 19:02 ` Glenn Morris
2013-02-23 20:10 ` Eli Zaretskii
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).