From: Eli Zaretskii <eliz@gnu.org>
To: Ami Fischman <ami@fischman.org>
Cc: alptekin.aker@gmail.com, 12745@debbugs.gnu.org
Subject: bug#12745: crash in bidi_pop_it during (idle) redisplay
Date: Wed, 31 Oct 2012 17:46:48 +0200 [thread overview]
Message-ID: <83fw4u7ifr.fsf@gnu.org> (raw)
In-Reply-To: <CAGKqTXWirPab35ebWxW8CWY+3X28AAMC6odG_5HHjKhN=UE9LQ@mail.gmail.com>
> Date: Tue, 30 Oct 2012 14:08:49 -0700
> From: Ami Fischman <ami@fischman.org>
> Cc: alptekin.aker@gmail.com, 12745@debbugs.gnu.org
>
> > Is it correct that the character at buffer position 1295 is a newline?
> >
>
> Yes.
>
>
> > Also, what are the values of the following?
> > it->stack[0].current
> >
>
> (gdb) p it->stack[0].current
> $63 = {
> pos = {
> charpos = 1295,
> bytepos = 1295
> },
> overlay_string_index = 0,
> string_pos = {
> charpos = -1,
> bytepos = -1
> },
> dpvec_index = -1
> }
>
> it->stack[0].string
> >
>
> (gdb) p it->stack[0].string
> $66 = 9755602
> (gdb) xtype
> Lisp_Symbol
> (gdb) xsymbol it->stack[0].string
> $67 = (struct Lisp_Symbol *) 0x94dbd0
> "nil"
>
> it->stack[0].method
> >
>
> (gdb) p it->stack[0].method
> $68 = GET_FROM_BUFFER
>
>
> > it->method
> >
>
> (gdb) p it->method
> $69 = GET_FROM_BUFFER
As expected.
I guess we need to wait for another crash, this time in the trunk
code, and take it from there. I will meanwhile fix
init_from_display_pos, because it's certainly looks broken, and could
well be the root cause for this.
Thanks.
next prev parent reply other threads:[~2012-10-31 15:46 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-28 3:31 bug#12745: crash in bidi_pop_it during (idle) redisplay Paul Eggert
2012-10-28 7:49 ` Paul Eggert
2012-10-28 7:50 ` Paul Eggert
2012-10-28 17:23 ` Eli Zaretskii
2012-10-28 19:00 ` Ami Fischman
2012-10-28 19:50 ` Eli Zaretskii
2012-10-29 4:26 ` Ami Fischman
2012-10-29 17:11 ` Eli Zaretskii
2012-10-29 17:56 ` Ami Fischman
2012-10-29 18:10 ` Eli Zaretskii
2012-10-29 18:29 ` Ami Fischman
2012-10-29 18:55 ` Eli Zaretskii
2012-10-29 18:56 ` Alp Aker
2012-10-29 19:09 ` Alp Aker
2012-10-29 19:23 ` Ami Fischman
2012-10-29 20:24 ` Eli Zaretskii
2012-10-29 20:57 ` Eli Zaretskii
2012-10-29 21:08 ` Ami Fischman
2012-10-30 17:52 ` Eli Zaretskii
2012-10-30 18:29 ` Ami Fischman
2012-10-30 21:00 ` Eli Zaretskii
2012-10-30 21:08 ` Ami Fischman
2012-10-31 15:46 ` Eli Zaretskii [this message]
2012-11-01 22:25 ` Ami Fischman
2012-11-02 7:17 ` Eli Zaretskii
2012-11-02 7:43 ` Ami Fischman
2012-11-03 9:31 ` Eli Zaretskii
2012-10-29 20:25 ` Eli Zaretskii
2012-10-29 20:42 ` Alp Aker
2012-10-29 20:59 ` Eli Zaretskii
2012-10-29 21:25 ` Alp Aker
2012-10-29 21:53 ` Alp Aker
2012-11-23 20:14 ` Ami Fischman
2012-11-23 21:56 ` Eli Zaretskii
2012-11-25 4:52 ` Ami Fischman
2012-11-25 16:51 ` Eli Zaretskii
2013-02-10 3:07 ` Glenn Morris
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=83fw4u7ifr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12745@debbugs.gnu.org \
--cc=alptekin.aker@gmail.com \
--cc=ami@fischman.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).