unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: 16163@debbugs.gnu.org
Subject: bug#16163: 24.3.50; segfault at xdisp.c 20044 -- (can not reproduce)
Date: Mon, 16 Dec 2013 19:01:50 +0200	[thread overview]
Message-ID: <8361qoenlt.fsf@gnu.org> (raw)
In-Reply-To: <87ob4gkg65.fsf@yahoo.fr>

> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> Date: Mon, 16 Dec 2013 15:45:54 +0100
> 
> I'm on trunk, and I had just pressed keys to run magit-status when this
> happened. Unfortunately my terminal window had a limit on the size of
> its history, so I lost the beginning of the gdb session.

To avoid such a loss, turn on logging inside GDB:

 (gdb) set logging on

Then everything GDB outputs will be echoed to a file named gdb.txt by
default.

> In the source at xdisp.c:20044 the code is :
> 	    row->glyphs[TEXT_AREA]->charpos = CHARPOS (it->position);
> 
> (gdb) bt
> #0  0x0809019e in display_line (it=0xbfff9898) at xdisp.c:20044
> #1  0x0809779f in try_window (window=165787789, pos=..., flags=1) at xdisp.c:16505

Not much to go by here, unfortunately.  You didn't even tell which
part of the above segfaulted: was it row->glyphs,
row->glyphs[TEXT_AREA]->charpos, or it->position?  Otherwise, what I
see as a routine redisplay cycle.

In addition, this seems to be an optimized build, so backtraces are
unreliable.  Please try reproducing this in an unoptimized build.

Thanks.





  reply	other threads:[~2013-12-16 17:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-16 14:45 bug#16163: 24.3.50; segfault at xdisp.c 20044 -- (can not reproduce) Nicolas Richard
2013-12-16 17:01 ` Eli Zaretskii [this message]
2013-12-17 10:33   ` Nicolas Richard
2013-12-17 16:10     ` Eli Zaretskii
2015-12-26  1:36     ` Lars Ingebrigtsen

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=8361qoenlt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=16163@debbugs.gnu.org \
    --cc=theonewiththeevillook@yahoo.fr \
    /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).