Subject: bug#16918: 24.3.50; emacs_backtrace.txt

From: Juanma Barranquero <[email-masked]>
Date: Sun, 2 Mar 2014 01:58:25 +0100

On Sun, Mar 2, 2014 at 1:00 AM, Drew Adams <[email-masked]> wrote:

> I think this was with this build:

Definitely, the backtrace does not make sense with the other build.

??
??:0
w32_backtrace at w32fns.c:8431
emacs_abort at w32fns.c:8463
terminate_due_to_signal at emacs.c:378
die at alloc.c:6761
row_equal_p at dispnew.c:1169
scrolling_window at dispnew.c:4070
update_window at dispnew.c:3392
update_window_tree at dispnew.c:3161
update_frame at dispnew.c:3059
redisplay_internal at xdisp.c:13748
redisplay at xdisp.c:12931
read_char at keyboard.c:2567
read_key_sequence at keyboard.c:9075
command_loop_1 at keyboard.c:1449
internal_condition_case at eval.c:1354
command_loop_2 at keyboard.c:1174
internal_catch at eval.c:1118
command_loop at keyboard.c:1153
recursive_edit_1 at keyboard.c:777
Frecursive_edit at keyboard.c:845
main at emacs.c:1646
?? at crt1.c:0
??
??:0
??
??:0
??
??:0