GNU bug report logs - #16660
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 16660 in the body.
You can then email your comments to 16660 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: Wed, 5 Feb 2014 13:31:32 -0800 (PST)

Backtrace:
011fb989
011fb9fa
010f003b
01161f9d
01009f22
0100a60f
01008963
010080f6
01007da0
010437c5
01041701
010f65f0
01103a81
010f4109
0117d091
010f3a3e
0117c63e
010f39a5
010f318c
010f3348
01180114
011c0d04
01180913
0118036d
0117f692
0117fbc7
0117a4b4
0117f1d9
0117a9a4
0117eb07
0117a72e
0117eb07
0117a9a4
0117c23a
0117eb07
0117a9a4
0116e47d
0117eb07
0117c892
0117eb07
0117a9a4
0117c13c
0117eb07
0117a9a4
0117eb07
0117a72e
0117eb07
0117a9a4
01180c42
01180440
0117f692
01180021
011c0d04
01180913
01180632
0117f010
0117a9a4
0117a7ec
0117eb07
0117a9a4
0117eb07
0117a72e
...




In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-02-02 on ODIEONE
Bzr revision: 116242 rudalics <at> gmx.at-20140202130041-n967dw77nw7ztvy9
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
 CPPFLAGS=-Ic:/Devel/emacs/include'

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

From: Juanma Barranquero <lekktu <at> gmail.com>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16660 <at> debbugs.gnu.org
Subject: Re: bug#16660: 24.3.50; emacs_backtrace.txt
Date: Thu, 6 Feb 2014 00:59:54 +0100

??
??:0
w32_backtrace at w32fns.c:8418
emacs_abort at w32fns.c:8450
terminate_due_to_signal at emacs.c:378
die at alloc.c:6761
add_row_entry at dispnew.c:4000
scrolling_window at dispnew.c:4204
update_window at dispnew.c:3392
update_window_tree at dispnew.c:3161
update_frame at dispnew.c:3059
redisplay_internal at xdisp.c:13665
redisplay at xdisp.c:12911
read_char at keyboard.c:2563
read_key_sequence at keyboard.c:9071
command_loop_1 at keyboard.c:1445
internal_condition_case at eval.c:1345
command_loop_2 at keyboard.c:1170
internal_catch at eval.c:1109
command_loop at keyboard.c:1141
recursive_edit_1 at keyboard.c:777
Frecursive_edit at keyboard.c:841
Ffuncall at eval.c:2803
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2974
Ffuncall at eval.c:2855
Fapply at eval.c:2345
apply1 at eval.c:2579
call_debugger at eval.c:323
eval_sub at eval.c:2259
Fprogn at eval.c:459
eval_sub at eval.c:2124
Fif at eval.c:410
eval_sub at eval.c:2124
Fprogn at eval.c:459
Fwhile at eval.c:989
eval_sub at eval.c:2124
Fprogn at eval.c:459
Fsave_excursion at editfns.c:941
eval_sub at eval.c:2124
Funwind_protect at eval.c:1206
eval_sub at eval.c:2124
Fprogn at eval.c:459
Flet at eval.c:967
eval_sub at eval.c:2124
Fprogn at eval.c:459
eval_sub at eval.c:2124
Fif at eval.c:410
eval_sub at eval.c:2124
Fprogn at eval.c:459
funcall_lambda at eval.c:3033
Ffuncall at eval.c:2867
Fapply at eval.c:2345
Ffuncall at eval.c:2787
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2974
apply_lambda at eval.c:2915
eval_sub at eval.c:2221
Fprogn at eval.c:459
Fif at eval.c:411
eval_sub at eval.c:2124
Fprogn at eval.c:459
eval_sub at eval.c:2124
Fif at eval.c:410
??
??:0

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16660 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#16660: 24.3.50; emacs_backtrace.txt
Date: Thu, 06 Feb 2014 07:50:16 +0200

> From: Juanma Barranquero <lekktu <at> gmail.com>
> Date: Thu, 6 Feb 2014 00:59:54 +0100
> Cc: 16660 <at> debbugs.gnu.org
> 
> w32_backtrace at w32fns.c:8418
> emacs_abort at w32fns.c:8450
> terminate_due_to_signal at emacs.c:378
> die at alloc.c:6761
> add_row_entry at dispnew.c:4000
> scrolling_window at dispnew.c:4204
> update_window at dispnew.c:3392
> update_window_tree at dispnew.c:3161
> update_frame at dispnew.c:3059
> redisplay_internal at xdisp.c:13665
> redisplay at xdisp.c:12911
> read_char at keyboard.c:2563

I see this happened while Emacs was in debugger.  Is this
reproducible?

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

From: Drew Adams <drew.adams <at> oracle.com>
To: Eli Zaretskii <eliz <at> gnu.org>, Juanma Barranquero <lekktu <at> gmail.com>
Cc: 16660 <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: RE: bug#16660: 24.3.50; emacs_backtrace.txt
Date: Wed, 5 Feb 2014 22:14:19 -0800 (PST)

> I see this happened while Emacs was in debugger.  Is this
> reproducible?

Not by me, I'm afraid.

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16660-done <at> debbugs.gnu.org, lekktu <at> gmail.com, drew.adams <at> oracle.com
Subject: Re: bug#16660: 24.3.50; emacs_backtrace.txt
Date: Thu, 06 Feb 2014 08:27:07 +0200

> Date: Wed, 5 Feb 2014 22:14:19 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: drew.adams <at> oracle.com, 16660 <at> debbugs.gnu.org
> 
> > I see this happened while Emacs was in debugger.  Is this
> > reproducible?
> 
> Not by me, I'm afraid.

Then I don't think we could do anything about this bug, sorry.
Resolving it needs careful examination of data structures used by the
display engine, to reveal what assumption (backed by the assertion
that was violated here) went wrong, and why.

Closing.

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

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 16660 <at> debbugs.gnu.org, martin rudalics <rudalics <at> gmx.at>,
 16691 <at> debbugs.gnu.org, drew.adams <at> oracle.com, lekktu <at> gmail.com
Subject: Re: bug#16691: 24.3.50; emacs_backtrace.txt
Date: Sat, 26 Dec 2015 14:26:32 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Mon, 10 Feb 2014 19:35:25 +0100
>> From: martin rudalics <rudalics <at> gmx.at>
>> CC: lekktu <at> gmail.com, drew.adams <at> oracle.com, 16691 <at> debbugs.gnu.org
>> 
>>  > If you meant row->y, then it is used in many different places,
>>  > including the display back-end,
>> 
>> Where is the display back-end?  If it's update_window
>
> It is _called_ by update_window.  In update_text_area, you will see
> the calls to rif->write_glyphs, which eventually calls the back-end
> (xterm.c, w32term.c, term.c, etc.).
>
>> we there set
>> 
>>        yb = window_text_bottom_y (w);
>> 
>> and then
>> 
>> 	  mode_line_row->y = yb;
>> 
>> so any prior notion of that row's y is lost.  And for the header line we
>> do
>> 
>> 	  header_line_row->y = 0;
>> 
>> But this still doesn't use row->y.  Where is the backend that uses
>> row->y to determine where on the screen to draw that row?
>
> Are you talking only about the mode line and the header line?  If so,
> then yes, those rows don't need the y coordinate, as they "know" where
> it is in advance.
>
> I thought you were asking a more general question about row->x and
> row->y.

It's unclear what the situation in this bug report is, or who is waiting
for more info from whom.  :-)  Is this still an issue?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 16660 <at> debbugs.gnu.org, rudalics <at> gmx.at, drew.adams <at> oracle.com,
 16691-done <at> debbugs.gnu.org, lekktu <at> gmail.com
Subject: Re: bug#16691: 24.3.50; emacs_backtrace.txt
Date: Sat, 26 Dec 2015 15:38:19 +0200

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Cc: martin rudalics <rudalics <at> gmx.at>,  16660 <at> debbugs.gnu.org,  16691 <at> debbugs.gnu.org,  lekktu <at> gmail.com,  drew.adams <at> oracle.com
> Date: Sat, 26 Dec 2015 14:26:32 +0100
> 
> It's unclear what the situation in this bug report is, or who is waiting
> for more info from whom.  :-)  Is this still an issue?

Not for me, I closed it long ago.

Closing again.

Previous Next

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