From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tobias.getzner@gmx.de, 20802@debbugs.gnu.org
Subject: bug#20802: Segfault when showing non-GTK+ tooltip
Date: Mon, 15 Jun 2015 18:00:55 +0200 [thread overview]
Message-ID: <557EF6B7.3000701@gmx.at> (raw)
In-Reply-To: <83zj41nhg9.fsf@gnu.org>
>> How are these supposed to
>> work when GLYPH_DEBUG is not defined?
>
> It cannot, obviously. Bug#17524 was reported in the GLYPH_DEBUG code:
> the assertion there segfaulted when it tried to access the image
> cache. So the code was fixed only for that situation.
Hmmm ... you should have told Michael back then. You clairvoyantly
identified the problem then as ...
But the real problem is that call to
x_free_frame_resources, which eventually calls free_frame_faces, which
decrements the image-cache refcount and frees the image cache, because
the refcount goes to zero.
... but the recipe ...
So I think the X version needs the same change I made in w32fns.c in
revision 117131, modulo the changes to the assertions.
... was misleading because the bug was triggerd without violating an
assertion. I doubt that Michael then build with glyph debugging enabled
because otherwise his fix should have helped indeed.
> IOW, that bug was mentioned as a source of ideas, not as something to
> copy verbatim to xfns.c. Sorry if I was unclear about that.
OK. One last question: In struct image_cache we specify refcount as
ptrdiff_t while w32fns.c defines image_cache_refcount as int. Both
xfns.c and nsfns.m define image_cache_refcount as ptrdiff_t. Shouldn't
we uniquify this?
martin
next prev parent reply other threads:[~2015-06-15 16:00 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 9:18 bug#20802: Segfault when showing non-GTK+ tooltip Tobias Getzner
2015-06-13 9:38 ` Eli Zaretskii
2015-06-13 10:25 ` martin rudalics
2015-06-13 10:54 ` Eli Zaretskii
2015-06-13 13:24 ` martin rudalics
2015-06-13 14:01 ` Eli Zaretskii
2015-06-13 14:28 ` martin rudalics
2015-06-13 14:42 ` Eli Zaretskii
2015-06-14 11:00 ` martin rudalics
2015-06-14 14:12 ` Eli Zaretskii
2015-06-15 8:22 ` martin rudalics
2015-06-15 15:01 ` Eli Zaretskii
2015-06-15 16:00 ` martin rudalics [this message]
2015-06-15 17:29 ` Eli Zaretskii
2015-06-16 13:30 ` martin rudalics
2015-06-16 14:54 ` Eli Zaretskii
2015-06-17 9:36 ` martin rudalics
2015-06-17 16:39 ` Eli Zaretskii
2015-06-17 18:56 ` Stefan Monnier
2015-06-18 13:37 ` martin rudalics
2015-06-18 15:53 ` Eli Zaretskii
2015-06-18 16:48 ` martin rudalics
2015-06-18 17:17 ` Eli Zaretskii
2015-06-18 17:36 ` martin rudalics
2015-06-18 18:00 ` Eli Zaretskii
2015-06-19 6:43 ` martin rudalics
2022-04-29 11:45 ` Lars Ingebrigtsen
2022-05-28 10:58 ` Lars Ingebrigtsen
2015-06-16 7:21 ` Tobias Getzner
2015-06-16 13:30 ` martin rudalics
2015-06-16 15:34 ` Tobias Getzner
2015-06-16 15:58 ` Eli Zaretskii
2015-06-16 16:34 ` Tobias Getzner
2015-06-16 17:12 ` Eli Zaretskii
2015-06-16 17:31 ` martin rudalics
2015-06-17 7:34 ` Tobias Getzner
2015-06-17 8:04 ` martin rudalics
2015-06-17 14:11 ` Tobias Getzner
2015-06-18 13:37 ` martin rudalics
2015-06-18 14:09 ` Tobias Getzner
2015-06-17 16:30 ` 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=557EF6B7.3000701@gmx.at \
--to=rudalics@gmx.at \
--cc=20802@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=tobias.getzner@gmx.de \
/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).