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: Thu, 31 Jan 2019 16:02:52 +0200 [thread overview]
Message-ID: <834l9o2acz.fsf@gnu.org> (raw)
In-Reply-To: <CAFyQvY2sER7FaA4zL_60R_hF2ndFE1aemr2qpMfsYLExZiDb+g@mail.gmail.com> (message from Kaushal Modi on Wed, 30 Jan 2019 15:54:06 -0500)
> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Wed, 30 Jan 2019 15:54:06 -0500
> Cc: 34256@debbugs.gnu.org
>
> > This says Emacs was trying to display an image, but what image is
> > that? Where did it come from?
>
>
> It's the inline image display in the Org mode buffer.
OK.
> > 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...
> >
>
> Imagemagick is probably not getting invoked.
>
> Org is using this part of the code to create image overlays:
> https://code.orgmode.org/bzg/org-mode/src/8ba23b9ce18d947a0241017ff33015a7807f615d/lisp/org.el#L18630-L18631
> .
>
> (create-image file
> (and width 'imagemagick)
> nil
> :width width)
>
> That `width' variable is nil, so effectively this is happening:
>
> (create-image file nil nil :width nil)
OK, so image resizing is still a suspect. Do you have HAVE_XRENDER
defined in src/config.h?
> > (gdb) frame 2
> > (gdb) p *s->first_glyph
> >
>
> Here it is:
>
> (gdb) frame 2
> #2 0x00000000004378fe in fill_image_glyph_string (s=s@entry=0x7fffffff7aa0)
> at xdisp.c:26154
> 26154 eassert (s->img);
> (gdb) p *s->first_glyph
> $1 = {
> charpos = 50512,
> object = XIL(0x47ba435),
> pixel_width = 404,
> ascent = 80,
> descent = 81,
> voffset = 0,
> type = 3,
> [...]
> u = {
> ch = 0,
> cmp = {
> automatic = false,
> id = 0
> },
> img_id = 0,
img_id = 0 is unusual for an image in a buffer. Are you running with
the tool bar disabled, perhaps?
And what do these show in the same call-stack frame #2:
(gdb) p FRAME_IMAGE_CACHE (s->f)->used
(gdb) p FRAME_IMAGE_CACHE (s->f)->images[0]
Thanks.
next prev parent reply other threads:[~2019-01-31 14:02 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
2019-01-30 20:54 ` Kaushal Modi
2019-01-31 14:02 ` Eli Zaretskii [this message]
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=834l9o2acz.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.