From: Eli Zaretskii <eliz@gnu.org>
To: Partha Pratim Ghosh <ghosh.parthapratim.unisa@gmail.com>
Cc: 45543@debbugs.gnu.org
Subject: bug#45543: 26.3; Segmentation Fault on mu4e
Date: Wed, 30 Dec 2020 19:05:21 +0200 [thread overview]
Message-ID: <83o8ibi5ri.fsf@gnu.org> (raw)
In-Reply-To: <87a6twl3nx.fsf@gmail.com> (message from Partha Pratim Ghosh on Tue, 29 Dec 2020 23:10:10 +0200)
> From: Partha Pratim Ghosh <ghosh.parthapratim.unisa@gmail.com>
> Date: Tue, 29 Dec 2020 23:10:10 +0200
>
> Stack trace of thread 2111:
> #0 0x00007f9e06a6e24b raise (libpthread.so.0 + 0x1524b)
> #1 0x00000000004feb7d n/a (emacs-gtk + 0xfeb7d)
> #2 0x0000000000517874 n/a (emacs-gtk + 0x117874)
> #3 0x0000000000517aad n/a (emacs-gtk + 0x117aad)
> #4 0x0000000000517b2d n/a (emacs-gtk + 0x117b2d)
> #5 0x00007f9e06a6e3c0 __restore_rt (libpthread.so.0 + 0x153c0)
> #6 0x00007f9e06c9e66d n/a (libotf.so.0 + 0xf66d)
> #7 0x00007f9e06c9fd1f n/a (libotf.so.0 + 0x10d1f)
> #8 0x00007f9e06ca1957 OTF_drive_gpos_with_log (libotf.so.0 + 0x12957)
> #9 0x00000000005e2a4f n/a (emacs-gtk + 0x1e2a4f)
> #10 0x00007f9e06c54d07 n/a (libm17n-flt.so.0 + 0x2d07)
> #11 0x00007f9e06c5874f n/a (libm17n-flt.so.0 + 0x674f)
> #12 0x00007f9e06c5874f n/a (libm17n-flt.so.0 + 0x674f)
> #13 0x00007f9e06c580f7 n/a (libm17n-flt.so.0 + 0x60f7)
> #14 0x00007f9e06c5874f n/a (libm17n-flt.so.0 + 0x674f)
> #15 0x00007f9e06c59217 n/a (libm17n-flt.so.0 + 0x7217)
Looks like a crash in libotf and/or libm17n-flt, which we no longer
use in Emacs 27 and later. Would it be possible for you to try Emacs
27.1 or the pretest of Emacs 27.2?
next prev parent reply other threads:[~2020-12-30 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 21:10 bug#45543: 26.3; Segmentation Fault on mu4e Partha Pratim Ghosh
2020-12-30 17:05 ` Eli Zaretskii [this message]
[not found] ` <875z4iq8q8.fsf@gmail.com>
2020-12-31 16:36 ` Eli Zaretskii
2021-01-01 20:24 ` Partha Pratim Ghosh
2021-01-01 20:46 ` Eli Zaretskii
2021-01-27 7:04 ` Lars Ingebrigtsen
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=83o8ibi5ri.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=45543@debbugs.gnu.org \
--cc=ghosh.parthapratim.unisa@gmail.com \
/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.