From: Eli Zaretskii <eliz@gnu.org>
To: Leo <sdl.web@gmail.com>
Cc: 11417@debbugs.gnu.org
Subject: bug#11417: 24.0.96; infinite looping in xdisp.c
Date: Mon, 07 May 2012 20:25:05 +0300 [thread overview]
Message-ID: <83havr3nv2.fsf@gnu.org> (raw)
In-Reply-To: <m162c83r05.fsf@gmail.com>
> From: Leo <sdl.web@gmail.com>
> Cc: 11417@debbugs.gnu.org
> Date: Tue, 08 May 2012 00:17:14 +0800
>
> I run gdb in emacs/src and attach to the process that is hanging. Then
> source .gdbinit and I got:
>
> DISPLAY = /tmp/launch-VtT4mU/org.x:0
> TERM = xterm-color
> [0] cancel
> [1] all
>
> Non-debugging symbols:
> [2] -[CIContext abort]
> [3] -[CIContextImpl abort]
> [4] abort
> > Argument required (one or more choice numbers).
You should type 1 or 4 at this point. If that doesn't help, simply
delete the offending line, viz.
break abort
> So commands such as xbt, xtype and pgrowx not working properly.
Too bad, I really need to see the glyph row that corresponds to the
problematic screen line, and perhaps the one before and after it
(that's what the pgrowx command does). Please see if you can provide
that information, after you succeed in reading .gdbinit.
> The rest is as attached. The portion of the line from it2.current
> should show:
>
> from distutils.core import setup, Extension
Which part(s) of this come from an overlay string? This info:
> (gdb) p it2.current
> $7 = {
> pos = {
> charpos = 411,
> bytepos = 411
> },
> overlay_string_index = 0,
> string_pos = {
> charpos = 1,
> bytepos = 1
> },
> dpvec_index = -1
> }
> (gdb) p it2.method
> $9 = GET_FROM_STRING
indicates that it2 bumped into a string while iterating over the
buffer. Once the x* commands work for you, you can display that
string as follows:
(gdb) p it2.string
(gdb) xstring
I need to know at which buffer positions there are overlay strings in
the offending line and in its neighbors.
Thanks.
next prev parent reply other threads:[~2012-05-07 17:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 4:24 bug#11417: 24.0.96; infinite looping in xdisp.c Leo
2012-05-06 5:43 ` Chong Yidong
2012-05-06 16:18 ` Eli Zaretskii
2012-05-07 16:17 ` Leo
2012-05-07 17:25 ` Eli Zaretskii [this message]
2012-05-07 18:39 ` Leo
2012-05-07 19:21 ` Eli Zaretskii
2012-05-07 19:42 ` Leo
2012-05-08 3:37 ` Chong Yidong
2012-05-08 17:26 ` Eli Zaretskii
2012-05-10 9:15 ` Leo
2012-05-10 17:43 ` Eli Zaretskii
2012-05-10 18:26 ` Eli Zaretskii
2012-05-11 10:00 ` Leo
2012-05-12 10:45 ` Eli Zaretskii
2012-05-13 1:34 ` Chong Yidong
2012-05-13 15:37 ` Eli Zaretskii
2012-05-13 8:54 ` Leo
2012-05-13 15:38 ` Eli Zaretskii
2012-05-15 6:33 ` Leo
2012-05-15 15:57 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83havr3nv2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11417@debbugs.gnu.org \
--cc=sdl.web@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.