all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 34256@debbugs.gnu.org
Subject: bug#34256: 27.0.50; Crash on draw_glyphs()
Date: Wed, 30 Jan 2019 20:55:21 +0200	[thread overview]
Message-ID: <83bm3y0ycm.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY3AyYCprP7bFWxkRDKS1Lk+2gbnjXX_FYYY5yEXtZ2KJA@mail.gmail.com> (message from Kaushal Modi on Wed, 30 Jan 2019 13:22:01 -0500)

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Wed, 30 Jan 2019 13:22:01 -0500
> Cc: 34256@debbugs.gnu.org
> 
> - I cannot reproduce the crash in an emacs -Q session using the same Org file, or even using my full
> unaltered config (except for commenting out desktop loading).
> 
> But now I have this detailed backtrace; hopefully it helps you spot the problem:
> 
> xdisp.c:26154: Emacs fatal error: assertion failed: s->img
> 
> Thread 1 "emacs" hit Breakpoint 1, terminate_due_to_signal (sig=sig@entry=6,
>     backtrace_limit=backtrace_limit@entry=2147483647) at emacs.c:370
> 370     {
> (gdb) bt
> #0  terminate_due_to_signal (sig=sig@entry=6, backtrace_limit=backtrace_limit@entry=2147483647) at
> emacs.c:370
> #1  0x00000000005a1622 in die (msg=msg@entry=0x67dc2c "s->img", file=file@entry=0x67dbaa "xdisp.c",
> line=line@entry=26154) at alloc.c:7453
> #2  0x00000000004378fe in fill_image_glyph_string (s=s@entry=0x7fffffff7aa0) at xdisp.c:26154
> #3  0x00000000004708cf in draw_glyphs (w=w@entry=0x13fa4e0, x=44, row=0x234ba50,
> area=area@entry=TEXT_AREA, start=<optimized out>, start@entry=0, end=end@entry=6,
> hl=DRAW_NORMAL_TEXT, overlaps=0)
>     at xdisp.c:26841

This says Emacs was trying to display an image, but what image is
that?  Where did it come from?  And could it be that the new native
image scaling is the reason for this (i.e., was the image supposed to
be resized)?  Hmm, but you built with ImageMagick, which AFAIU means
the native  resizing code should not be invoked...

> - The Org file/buffer seen when this crash happens displays inline images.

Please show the relevant parts of the file anyway.

Also, in this callstack frame:

  #2  0x00000000004378fe in fill_image_glyph_string (s=s@entry=0x7fffffff7aa0) at xdisp.c:26154

please show the full contents of s->first_glyph.  Like this:

  (gdb) frame 2
  (gdb) p *s->first_glyph






  reply	other threads:[~2019-01-30 18:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 14:30 bug#34256: 27.0.50; Crash on draw_glyphs() Kaushal Modi
2019-01-30 16:16 ` Eli Zaretskii
2019-01-30 16:35   ` Kaushal Modi
2019-01-30 16:51     ` Eli Zaretskii
2019-01-30 18:22       ` Kaushal Modi
2019-01-30 18:55         ` Eli Zaretskii [this message]
2019-01-30 20:54           ` Kaushal Modi
2019-01-31 14:02             ` Eli Zaretskii
2019-01-31 15:50               ` Kaushal Modi
2019-01-31 16:52                 ` Eli Zaretskii
2019-01-31 17:02                   ` Kaushal Modi
2019-01-31 17:05                     ` Kaushal Modi
2019-01-31 20:26                     ` Eli Zaretskii
2019-02-01  3:15                       ` Kaushal Modi
2019-02-01  3:25                         ` Kaushal Modi
2019-02-01  8:41                           ` Eli Zaretskii
2019-02-04 16:03                             ` Kaushal Modi
2019-02-04 17:50                               ` 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=83bm3y0ycm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=34256@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 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.