From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 17322@debbugs.gnu.org
Subject: bug#17322: 24.3.90; emacs crash at eassert (verify_row_hash (a)) in dispnew.c:1169
Date: Wed, 23 Apr 2014 16:54:27 +0200 [thread overview]
Message-ID: <5357D423.1030507@yahoo.fr> (raw)
In-Reply-To: <83k3ag9kdb.fsf@gnu.org>
Le 23/04/2014 16:43, Eli Zaretskii a écrit :
>> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
>> Breakpoint 1, terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:351
>> 351 signal (sig, SIG_DFL);
>> #0 terminate_due_to_signal (sig=6, backtrace_limit=2147483647) at emacs.c:351
>> #1 0x081f5927 in die (msg=0x82d5798 "verify_row_hash (a)", file=0x82d5608 "dispnew.c", line=1169) at alloc.c:6826
>> #2 0x08059979 in row_equal_p (a=0xa25151c, b=0xb2a0afc, mouse_face_p=true) at dispnew.c:1169
>> #3 0x0805ef01 in scrolling_window (w=0xa7ee2f0, header_line_p=false) at dispnew.c:4129
>
> There's a slim chance that output from the following GDB commands will
> give some hint:
>
> (gdb) frame 2
> (gdb) pgrowx a
> (gdb) pgrowx b
(gdb) frame 2
#2 0x08059979 in row_equal_p (a=0xa25151c, b=0xb2a0afc, mouse_face_p=true) at dispnew.c:1169
1169 eassert (verify_row_hash (a));
(gdb) pgrowx a
TEXT: 19 glyphs
0 0: CHAR[7] pos=993 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
1 9: CHAR[1] pos=994 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
2 18: CHAR[0] pos=995 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
3 27: CHAR[e] pos=996 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
4 36: CHAR[e] pos=997 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
5 45: CHAR[8] pos=998 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
6 54: CHAR[7] pos=999 blev=0,btyp=L w=9 a+d=14+5 face=36 MB
7 63: CHAR[ ] pos=1000 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
8 72: CHAR[*] pos=1001 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
9 81: CHAR[ ] pos=1002 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
10 90: CHAR[c] pos=1003 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
11 99: CHAR[ ] pos=1004 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
12 108: CHAR[o] pos=1005 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
13 117: CHAR[ ] pos=1006 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
14 126: CHAR[l] pos=1007 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
15 135: CHAR[d] pos=1008 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
16 144: CHAR[l] pos=1009 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
17 153: CHAR[c] pos=1010 blev=0,btyp=L w=9 a+d=14+5 face=26 MB
18 162: CHAR[ ] pos=0 blev=0,btyp=B w=9 a+d=14+5 face=26 MB
RIGHT: 1 glyphs
0 171: COMP[0 (32776..21)] pos=-1 w=1012 a+d=0+-9539 face=5 vof=2388 MB slice=32776,0,21,0
(gdb) pgrowx b
TEXT: 19 glyphs
0 0: CHAR[7] pos=993 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
1 9: CHAR[1] pos=994 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
2 18: CHAR[0] pos=995 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
3 27: CHAR[e] pos=996 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
4 36: CHAR[e] pos=997 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
5 45: CHAR[8] pos=998 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
6 54: CHAR[7] pos=999 blev=0,btyp=L w=9 a+d=14+5 face=21 MB
7 63: CHAR[ ] pos=1000 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
8 72: CHAR[*] pos=1001 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
9 81: CHAR[ ] pos=1002 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
10 90: CHAR[c] pos=1003 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
11 99: CHAR[ ] pos=1004 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
12 108: CHAR[o] pos=1005 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
13 117: CHAR[ ] pos=1006 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
14 126: CHAR[l] pos=1007 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
15 135: CHAR[d] pos=1008 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
16 144: CHAR[l] pos=1009 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
17 153: CHAR[c] pos=1010 blev=0,btyp=L w=9 a+d=14+5 face=11 MB
18 162: CHAR[ ] pos=0 blev=0,btyp=B w=9 a+d=14+5 MB
(gdb)
fwiw, the chars in the brackets above correspond to a git abbreviated sha1 and a commit message as displayed e.g. in magit log buffers.
>> #3 0x0805ef01 in scrolling_window (w=0xa7ee2f0, header_line_p=false) at dispnew.c:4129
>> desired_matrix = 0x96873a0
>> current_matrix = 0xb453fb0
>> yb = 967
>> i = 32
>> j = 32
>> first_old = 30
>> first_new = 30
>> last_old = 50
>> last_new = 50
>
> Do you really have 50 lines in your windows?
I apparently do, at least in my current session (the 51st can be seen but the buffer text scrolls up when cursor reaches it).
--
Nico.
next prev parent reply other threads:[~2014-04-23 14:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 10:57 bug#17322: 24.3.90; emacs crash at eassert (verify_row_hash (a)) in dispnew.c:1169 Nicolas Richard
2014-04-23 14:43 ` Eli Zaretskii
2014-04-23 14:54 ` Nicolas Richard [this message]
2014-04-23 15:35 ` Eli Zaretskii
2014-04-23 15:49 ` Nicolas Richard
2014-04-23 16:20 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5357D423.1030507@yahoo.fr \
--to=theonewiththeevillook@yahoo.fr \
--cc=17322@debbugs.gnu.org \
--cc=eliz@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).