From: Eli Zaretskii <eliz@gnu.org>
To: Helmut Eller <eller.helmut@gmail.com>
Cc: 9436@debbugs.gnu.org
Subject: bug#9436: 24.0.50; Segmentation fault during redisplay
Date: Mon, 05 Sep 2011 00:20:23 -0400 [thread overview]
Message-ID: <E1R0QfX-0006Mj-4Z@fencepost.gnu.org> (raw)
In-Reply-To: <m2zkikndft.fsf@gmail.com> (message from Helmut Eller on Mon, 05 Sep 2011 00:35:34 +0200)
> From: Helmut Eller <eller.helmut@gmail.com>
> Date: Mon, 05 Sep 2011 00:35:34 +0200
>
> I updated the source tree and configured with
> `configure '--with-gif=no' '--with-gnutls=no' 'CFLAGS=-g3 -O0''
Please reconfigure like this:
configure --enable-asserts --enable-checking --with-gif=no --with-gnutls=no 'CFLAGS=-g3 -O0'
This will enable several important sanity checks and hopefully allow
us to see why the frame pointer is NULL. Please try again after
rebuilding Emacs, and see if you get an abort somewhere, or the same
segfault.
> Then started Emacs from gdb. After a while the it occurred again.
> it->f seems to be 0 here too:
>
> (gdb) frame 0
> #0 0x0807e455 in move_it_to (it=0xbfffd9d0, to_charpos=1688, to_x=-1,
> to_y=-1, to_vpos=-1, op=8) at xdisp.c:8444
> 8444 if (!FRAME_WINDOW_P (it->f)
> (gdb) p it->f
> $5 = (struct frame *) 0x0
If you go up 1 frame to here:
> #1 0x080865e7 in redisplay_internal () at xdisp.c:12814
And display w->frame there, is it also NULL? If so, can you display
the contents of the structure pointed to by w, and also compare that
with selected_window? Also, what is the value of current_buffer and
selected_frame?
When this happened, is it possible that you did something that
modified the display configuration, like killed a window or a frame or
changed the display dimensions?
next prev parent reply other threads:[~2011-09-05 4:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-04 17:53 bug#9436: 24.0.50; Segmentation fault during redisplay Helmut Eller
2011-09-04 18:21 ` Eli Zaretskii
2011-09-04 22:35 ` Helmut Eller
2011-09-05 4:20 ` Eli Zaretskii [this message]
2015-12-25 23:08 ` Lars Ingebrigtsen
2014-09-25 3:59 ` aidalgol
2014-09-25 8:02 ` 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=E1R0QfX-0006Mj-4Z@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=9436@debbugs.gnu.org \
--cc=eller.helmut@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.