From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: 22.0.50 SEGFAULT
Date: Fri, 15 Jul 2005 10:45:17 +0200 [thread overview]
Message-ID: <m3hdewwj8i.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <pan.2005.07.15.02.28.53.19721@as.arizona.edu> (JD Smith's message of "Thu, 14 Jul 2005 19:28:54 -0700")
JD Smith <jdsmith@as.arizona.edu> writes:
> I'm still getting SEGFAULTS in the most recent CVS build, relating to
> increment_row_positions. I had previously reported this was fixed in
> 22.0.50, but had not tested adequately. It is an intermittent
> SEGFAULT, usually triggered by a key comand that causes window
> redisplay. This is:
>
> GNU Emacs 22.0.50.3 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
> of 2005-07-14 on turtle.as.arizona.edu
>
> (gdb) run
> Starting program: /usr/local/bin/emacs -geometry 80x40+0+0
> Detaching after fork from child process 24951.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x08050c4f in increment_row_positions (row=0x8b865c8, delta=-1, delta_bytes=4)
> at dispnew.c:1190
> 1190 if (BUFFERP (row->glyphs[area][i].object)
BUFFERP(...) also examines the size of the glyph object, i.e. it
accesses something like this:
XVECTOR(row->glyphs[area][i].object)->size
So it seems that the glyph object (after stripping off bits and
pieces) points to void memory -- which should not happen.
The question is what object should have been there (if any)...
What was displayed in the window where this happened?
Next time this happens, pls. print the information from the following
gdb commands:
p *row
p i
p area
p row->glyphs[area][i]
p row->glyphs[area][i+1]
p row->glyphs[area][i-1] (if i > 0)
prow
up
p start
up
p first_unchanged_at_end_vpos
p dvpos
p dy
p *w
pwin
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-07-15 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 2:28 22.0.50 SEGFAULT JD Smith
2005-07-15 8:45 ` Kim F. Storm [this message]
2005-07-29 1:49 ` JD Smith
2005-07-30 23:01 ` Kim F. Storm
2005-08-03 16:19 ` JD Smith
2005-08-08 22:51 ` JD Smith
2005-09-19 23:18 ` JD Smith
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=m3hdewwj8i.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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 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.