From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Segfault in vertical-motion
Date: Tue, 06 Sep 2011 22:37:17 +0300 [thread overview]
Message-ID: <838vq1jwcy.fsf@gnu.org> (raw)
In-Reply-To: <4E666AA6.3050802@gmx.at>
> Date: Tue, 06 Sep 2011 20:47:02 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: emacs-devel@gnu.org
>
> > What is it->method at this point? It should be between 0 and 5 (see
> > enum it_method on dispextern.h).
>
> (gdb) p it->method
> $1 = 50116946
Garbage (I think this is Qnil, btw, but it->method cannot be a Lisp
object). And I see that this garbage goes all the way from
Fvertical_motion, as your original backtrace shows:
#4 0x010c2108 in Fvertical_motion (lines=4, window=56154629) at indent.c:2099
it_start = 81
first_x = 0
it_overshoot_expected = 0
it = {
window = 0,
w = 0x2c,
f = 0x35a0000,
method = 50116946, <<<<<<<<<<<<<<<<<<<<<<<<<<<<
So I think it would be good if you step through Fvertical_motion
(without stepping into the function it calls) after setting a
watchpoint on it.method, and see which call(s) change it. We can then
take it from there.
> > Also, what is it->current?
>
> (gdb) p it->current
> $2 = {
> pos = {
> charpos = 10,
> bytepos = 0
> },
Also garbage (bytepos cannot be zero, its minimum value is 1, and it
certainly cannot be smaller than charpos).
> I have to bisect my customizations first to know what's really
> causing it. This will take some time :-(
It may be a better idea to step through Fvertical_motion and see who
garbles the iterator object. It could lead us to solution faster and
more reliably, since you say the crash is 100% reproducible with your
~/.emacs.
next prev parent reply other threads:[~2011-09-06 19:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 12:56 Segfault in vertical-motion martin rudalics
2011-09-06 16:43 ` Eli Zaretskii
2011-09-06 18:47 ` martin rudalics
2011-09-06 19:37 ` Eli Zaretskii [this message]
2011-09-07 17:55 ` martin rudalics
2011-09-07 18:16 ` Eli Zaretskii
2011-09-07 18:51 ` martin rudalics
2011-09-07 18:56 ` Eli Zaretskii
2011-09-07 19:12 ` martin rudalics
2011-09-07 20:10 ` Eli Zaretskii
2011-09-08 7:03 ` martin rudalics
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=838vq1jwcy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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).