unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Manuel Giraud <manuel@ledu-giraud.fr>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 59802@debbugs.gnu.org
Subject: bug#59802: 30.0.50; Checkbox button not rendered
Date: Sat, 03 Dec 2022 19:16:51 +0100	[thread overview]
Message-ID: <87mt84gxnw.fsf@ledu-giraud.fr> (raw)
In-Reply-To: <83zgc4crg6.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 03 Dec 2022 19:44:41 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

[...]

> Does "M-x describe-text-properties RET" tell you what properties are there
> at the place where the checkboxes were supposed to be?  If so, request the
> details of the image that is the value of the 'display' property.
>
> Another possibility is to run under GDB with a breakpoint in svg_load, and
> then look at img->spec and the details of the image.

Now this is strange.  Here is what I get at the svg_load break point for
img:

--8<---------------cut here---------------start------------->8---
(gdb) p img
$2 = (struct image *) 0x10980e87d0
(gdb) p img->spec
Cannot access memory at address 0x10980e8860
--8<---------------cut here---------------end--------------->8---
-- 
Manuel Giraud





  reply	other threads:[~2022-12-03 18:16 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-03 10:40 bug#59802: 30.0.50; Checkbox button not rendered Manuel Giraud
2022-12-03 11:29 ` Eli Zaretskii
2022-12-03 14:47   ` Manuel Giraud
2022-12-03 17:44     ` Eli Zaretskii
2022-12-03 18:16       ` Manuel Giraud [this message]
2022-12-03 18:22         ` Eli Zaretskii
2022-12-03 18:24       ` Manuel Giraud
2022-12-03 18:49         ` Eli Zaretskii
2022-12-03 21:32           ` Manuel Giraud
2022-12-04  7:02             ` Eli Zaretskii
2022-12-09 12:26               ` Manuel Giraud
2022-12-09 12:35                 ` Eli Zaretskii
2022-12-09 13:41                   ` Stephen Berman
2022-12-09 14:07                     ` Manuel Giraud
2022-12-09 14:14                       ` Stephen Berman
2022-12-10 13:49                     ` Eli Zaretskii
2022-12-10 16:24                       ` Stephen Berman
2022-12-10 17:04                         ` Eli Zaretskii
2022-12-10 17:57                           ` Manuel Giraud
2022-12-10 18:38                             ` Eli Zaretskii
2022-12-11 13:12                           ` Stephen Berman
2022-12-11 14:47                             ` Eli Zaretskii
2022-12-11 15:54                             ` Eli Zaretskii
2022-12-11 22:40                               ` Stephen Berman
2022-12-12 17:42                                 ` Eli Zaretskii
2022-12-12 23:38                                   ` Stephen Berman
2022-12-12 12:33                               ` Manuel Giraud
2022-12-12 16:56                               ` Manuel Giraud
2022-12-12 17:25                                 ` Stephen Berman
2022-12-12 17:38                                 ` Eli Zaretskii
2022-12-13  9:21                                   ` Manuel Giraud
2022-12-13 10:16                                     ` Stephen Berman
2022-12-13 12:49                                     ` Eli Zaretskii
2022-12-13 16:16                                       ` Manuel Giraud
2022-12-13 16:40                                         ` Eli Zaretskii
2022-12-13 17:15                                           ` Manuel Giraud
2022-12-13 17:36                                             ` Eli Zaretskii
2022-12-16  8:27                                               ` Manuel Giraud
2022-12-16 15:51                                                 ` Eli Zaretskii
2022-12-16 16:09                                                   ` Manuel Giraud
2022-12-09 13:57                   ` Manuel Giraud
2022-12-10 13:47                     ` Eli Zaretskii
2022-12-10 14:26                       ` Manuel Giraud

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=87mt84gxnw.fsf@ledu-giraud.fr \
    --to=manuel@ledu-giraud.fr \
    --cc=59802@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).