unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: James Ferguson <james@faff.org>, 54661@debbugs.gnu.org
Subject: bug#54661: 29.0.50; Emacs SEGV in get_glyph_face_and_encoding
Date: Sat, 30 Apr 2022 19:28:59 +0200	[thread overview]
Message-ID: <87r15ev5t0.fsf@gnus.org> (raw)
In-Reply-To: <83mth55k0c.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Apr 2022 10:40:35 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> Can you try figuring that out?  One way of doing so is to set up a
> breakpoint in free_realized_faces, here:
>
>       for (i = 0; i < c->used; ++i)  <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
> 	{
> 	  free_realized_face (f, c->faces_by_id[i]);
> 	  c->faces_by_id[i] = NULL;
> 	}
>
> and enable this breakpoint only between the above two lines of
> xdisp.c.  (You can do that via breakpoint commands of 2 more
> breakpoints in xdisp.c, in the places I mentioned above: a breakpoint
> on xdisp.c:16531 with commands that enable the breakpoint in
> free_realized_face, and another on xdisp.c:16598 which disables that
> breakpoint.)  Then in the breakpoint commands for the breakpoint in
> free_realized_face, produce the C and Lisp backtrace (the latter with
> xbacktrace command defined on src/.gdbinit), and post it here.  That
> might tell us which code is doing this.

This was a month ago, and there wasn't any response, so I guess there's
little chance that there'll be any development in this bug report, so
I'm closing it.  If progress can be made, please respond to the debbugs
address and we'll reopen.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-04-30 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 21:19 bug#54661: 29.0.50; Emacs SEGV in get_glyph_face_and_encoding James Ferguson
2022-04-01  7:40 ` Eli Zaretskii
2022-04-30 17:28   ` Lars Ingebrigtsen [this message]

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=87r15ev5t0.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=54661@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=james@faff.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).