From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 34256@debbugs.gnu.org
Subject: bug#34256: 27.0.50; Crash on draw_glyphs()
Date: Thu, 31 Jan 2019 10:50:26 -0500 [thread overview]
Message-ID: <CAFyQvY2z=nO60_iUSadjkutHV+1oKuBSMJ_Vau-Fs8qsi6bLzQ@mail.gmail.com> (raw)
In-Reply-To: <834l9o2acz.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 693 bytes --]
On Thu, Jan 31, 2019 at 9:03 AM Eli Zaretskii <eliz@gnu.org> wrote:
>
> OK, so image resizing is still a suspect. Do you have HAVE_XRENDER
> defined in src/config.h?
>
Yes, I do. Here is the full config.h: https://ptpb.pw/ls2f
> > img_id = 0,
>
> img_id = 0 is unusual for an image in a buffer. Are you running with
> the tool bar disabled, perhaps?
>
Yes, I am! I am hiding both tool and menu bars.
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]
>
(gdb) p FRAME_IMAGE_CACHE (s->f)->used
$2 = 2
(gdb) p FRAME_IMAGE_CACHE (s->f)->images[0]
$3 = (struct image *) 0x0
Thank you.
[-- Attachment #2: Type: text/html, Size: 1518 bytes --]
next prev parent reply other threads:[~2019-01-31 15:50 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
2019-01-31 15:50 ` Kaushal Modi [this message]
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
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='CAFyQvY2z=nO60_iUSadjkutHV+1oKuBSMJ_Vau-Fs8qsi6bLzQ@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=34256@debbugs.gnu.org \
--cc=eliz@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 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).