From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Dr. Arne Babenhauserheide" <arne_bab@web.de>, 43943@debbugs.gnu.org
Subject: bug#43943: >=27.1; segfault with package-list-packages and others
Date: Mon, 12 Oct 2020 19:33:20 +0200 [thread overview]
Message-ID: <m2r1q3l57j.fsf@gmail.com> (raw)
In-Reply-To: <83eem32w8u.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Oct 2020 20:24:17 +0300")
>>>>> On Mon, 12 Oct 2020 20:24:17 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
>> Cc: 43943@debbugs.gnu.org
>> Date: Mon, 12 Oct 2020 18:32:11 +0200
>>
>> > My guess is that it was the fontconfig cache.
>>
>> Can something be done to prevent a segfault in this case?
Eli> Most probably, but we need more data about the cause(s), so until you
Eli> or someone else reproduces the problem and provides the additional
Eli> data, I don't see how we can make any progress. Your build was
Eli> stripped of debug symbols, so we don't even know in which source line
Eli> the crash happened, and cannot make any intelligent guesses why that
Eli> could happen.
Eli> Another important detail is the font that was being opened at the
Eli> point of the crash.
Eli> So if you or someone else can provide these details, I'm sure we will
Eli> find the culprit soon enough. It could even be that this is already
Eli> solved in the development sources.
bug#41627 perhaps? Iʼd test it, but my GNU/Linux box is terminal ATM.
Robert
--
next prev parent reply other threads:[~2020-10-12 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 6:04 bug#43943: 27.1; segfault with package-list-packages and others Dr. Arne Babenhauserheide
2020-10-12 8:39 ` bug#43943: >=27.1; " Dr. Arne Babenhauserheide
2020-10-12 15:00 ` Eli Zaretskii
2020-10-12 16:32 ` Dr. Arne Babenhauserheide
2020-10-12 17:24 ` Eli Zaretskii
2020-10-12 17:33 ` Robert Pluim [this message]
2020-10-12 18:43 ` Dr. Arne Babenhauserheide
2020-10-12 18:46 ` Dr. Arne Babenhauserheide
2020-10-12 18:48 ` Dr. Arne Babenhauserheide
2020-10-12 19:10 ` Eli Zaretskii
2020-10-12 19:28 ` Dr. Arne Babenhauserheide
2020-11-16 3:19 ` Stefan Kangas
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=m2r1q3l57j.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=43943@debbugs.gnu.org \
--cc=arne_bab@web.de \
--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).