unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <md5i@md5i.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11199@debbugs.gnu.org
Subject: bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state
Date: Sun, 08 Apr 2012 16:49:14 -0400	[thread overview]
Message-ID: <87hawuar05.fsf@maru.md5i.com> (raw)
In-Reply-To: <83wr5q7yf1.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 08 Apr 2012 23:37:22 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Michael Welsh Duggan <md5i@md5i.com>
>> Cc: mituharu@math.s.chiba-u.ac.jp,  11199@debbugs.gnu.org
>> Date: Sun, 08 Apr 2012 16:25:46 -0400
>> 
>> >> (gdb) pgrowx last_unchanged_at_beg_row
>> >> TEXT: 68 glyphs
>> >>   0    0: CHAR[ ] pos=237 blev=0,btyp=L w=8 a+d=12+3 MB
>> >> ...
>> >>  66  528: CHAR[)] pos=303 blev=0,btyp=L w=8 a+d=12+3 MB
>> >>  67  536: CHAR[ ] pos=0 blev=0,btyp=B w=8 a+d=12+3 MB
>> >> (gdb) prowlims last_unchanged_at_beg_row
>> >> edges=(237,305),r2l=0,cont=0,trunc=(0,0),at_zv=0
>> >> (gdb) 
>> >
>> > And what does the following produce in this frame?
>> >
>> >   (gdb) p row->end
>> 
>> (gdb) p row->end
>> $8 = {
>>   pos = {
>>     charpos = 309, 
>>     bytepos = 313
>>   }, 
>
> That's the problem: the end position does not correspond to the actual
> buffer positions of the characters in the glyph row (which are 237 to
> 303).  But how could that happen?..  And why doesn't it happen to me?
> I cannot even make init_to_row_end be called when I type C-k.
>
> Btw, if you set bidi-display-reordering nil in *scratch* before typing
> the recipe, does the crash still happen?

It does not.  If you need me to poke around just point me in the right
direction.

-- 
Michael Welsh Duggan
(md5i@md5i.com)





  parent reply	other threads:[~2012-04-08 20:49 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-08  2:26 bug#11199: 24.0.95; killing right-to-left text at eob leads to inconsistent state YAMAMOTO Mitsuharu
2012-04-08  7:33 ` Eli Zaretskii
2012-04-08 18:28   ` Michael Welsh Duggan
2012-04-08 18:33     ` Michael Welsh Duggan
2012-04-08 20:03     ` Eli Zaretskii
2012-04-08 20:13       ` Eli Zaretskii
2012-04-08 20:19         ` Michael Welsh Duggan
2012-04-08 20:16       ` Michael Welsh Duggan
2012-04-08 20:20         ` Eli Zaretskii
2012-04-08 20:25           ` Michael Welsh Duggan
2012-04-08 20:37             ` Eli Zaretskii
2012-04-08 20:48               ` Eli Zaretskii
2012-04-08 21:01                 ` Michael Welsh Duggan
2012-04-08 21:10                   ` Eli Zaretskii
2012-04-08 21:17                     ` Michael Welsh Duggan
2012-04-09  6:24                       ` Eli Zaretskii
2012-04-08 20:49               ` Michael Welsh Duggan [this message]
2012-04-08 21:07                 ` Eli Zaretskii
2012-04-09  8:21                   ` YAMAMOTO Mitsuharu
2012-04-09  9:32                     ` Eli Zaretskii
2012-04-09  9:10             ` Eli Zaretskii
2012-04-09  9:48               ` YAMAMOTO Mitsuharu
2012-04-09 10:17                 ` Eli Zaretskii
2012-04-09 11:07                   ` Eli Zaretskii
2012-04-09 11:52                     ` Eli Zaretskii
2012-04-09 12:18                       ` Michael Welsh Duggan
2012-04-09 12:34                         ` Eli Zaretskii
2012-04-09 23:50                           ` YAMAMOTO Mitsuharu
2012-04-10  6:27                             ` 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=87hawuar05.fsf@maru.md5i.com \
    --to=md5i@md5i.com \
    --cc=11199@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).