all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Maikol Solís" <maikol.solis@ucr.ac.cr>
Cc: 45511@debbugs.gnu.org
Subject: bug#45511: 27.1; Emacs crashes in gui_produce_glyphs when using a custom function for org-roam-insert
Date: Mon, 28 Dec 2020 19:16:07 +0200	[thread overview]
Message-ID: <83r1n9kg14.fsf@gnu.org> (raw)
In-Reply-To: <CAKyh8EbCX5p8NFj+2Kf7R3iuSTqiRA8a4BT3K5hMnYLndaanmw@mail.gmail.com> (message from Maikol Solís on Mon, 28 Dec 2020 09:32:17 -0600)

> From: Maikol Solís <maikol.solis@ucr.ac.cr>
> Date: Mon, 28 Dec 2020 09:32:17 -0600
> 
> Everything is fine except that after a couple of times using it, emacs crashes completely.  I think that is
> caused by this function because this has never happened before.
> 
> I used `gdb` to follow the crash and this is the output:
> 
>      Thread 1 "emacs-gtk" received signal SIGSEGV, Segmentation fault.

Is this a normal build of Emacs, or did you build some branch of the
Git repository?  (I'm puzzled why the thread is called "emacs-gtk".)

>      gui_produce_glyphs (it=0x7fff82fc3650) at xdisp.c:29925
>      29925         struct font *font = face->font;
>      (gdb) next

At this point, please say

   (gdb) source /path/to/emacs/src/.gdbinit
   (gdb) bt

(replacing "/path/to/emacs" with the real location of the Emacs
sources on your system) and post the result.





  reply	other threads:[~2020-12-28 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 15:32 bug#45511: 27.1; Emacs crashes in gui_produce_glyphs when using a custom function for org-roam-insert Maikol Solís
2020-12-28 17:16 ` Eli Zaretskii [this message]
2020-12-28 18:42   ` Maikol Solís
2020-12-28 19:28     ` Eli Zaretskii
2020-12-28 21:30       ` Maikol Solís

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=83r1n9kg14.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=45511@debbugs.gnu.org \
    --cc=maikol.solis@ucr.ac.cr \
    /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.