unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 29031@debbugs.gnu.org
Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config
Date: Mon, 30 Oct 2017 20:22:04 +0200	[thread overview]
Message-ID: <83r2tkts1f.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2o+q0tUQqqXgiX+m0x+cBb-MiezfZq2WCJo=ZLEXmZoQ@mail.gmail.com> (message from Kaushal Modi on Mon, 30 Oct 2017 14:17:57 +0000)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Mon, 30 Oct 2017 14:17:57 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>
> 
> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
> 0x000000000043d101 in append_glyph (it=0x7fffffff2390) at xdisp.c:25880

Line 25880 of xdisp.c is this:

      glyph->charpos = CHARPOS (it->position);

So what is the problematic data here?  Is 'glyph' a NULL pointer or
something?  Or is 'it' a garbled pointer?  What do these commands
show:

  (gdb) p glyph
  (gdb) p glyph->charpos
  (gdb) p it->position

Basically, I need you to run this under a debugger and answer several
questions.  Bonus points for reproducing this in an unoptimized build
configured with --enable-checking='yes,glyphs', and then showing the
backtrace from the segfault.

IOW, this problem needs to be debugged, and for that we need data that
explains the crash.  Could you please help in collecting that data?

Thanks.





  parent reply	other threads:[~2017-10-30 18:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-27 21:24 bug#29031: 25.3; Segmentation fault when starting emacs with my config Kaushal Modi
2017-10-30 14:17 ` Kaushal Modi
2017-10-30 16:03   ` Kaushal Modi
2017-10-30 18:37     ` Eli Zaretskii
2017-10-30 19:24       ` Kaushal Modi
2017-10-30 19:34         ` Eli Zaretskii
2017-10-30 19:51         ` Eli Zaretskii
2017-10-30 21:36           ` Kaushal Modi
2017-10-31 20:26             ` Eli Zaretskii
2017-10-31 20:52               ` Kaushal Modi
2017-10-31 20:56                 ` Eli Zaretskii
2017-11-07 13:27                 ` Noam Postavsky
2017-11-07 13:30                   ` Kaushal Modi
2017-11-07 13:55                     ` Noam Postavsky
2017-10-30 18:22   ` Eli Zaretskii [this message]
2017-10-30 18:34     ` Kaushal Modi
2017-10-30 18:52       ` Eli Zaretskii
2017-10-30 18:57         ` Kaushal Modi
2017-10-30 19:18           ` Kaushal Modi
2017-10-30 19:28             ` Eli Zaretskii
2019-09-29  0:44 ` Stefan Kangas
2019-09-29  0:58   ` Noam Postavsky
2019-09-29  7:26     ` Eli Zaretskii
2019-10-30 20:17   ` Stefan Kangas
2019-10-30 20:47     ` Kaushal Modi
2019-10-30 21:16       ` Stefan Kangas

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=83r2tkts1f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=29031@debbugs.gnu.org \
    --cc=kaushal.modi@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 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).