From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: FreeCAD does not launch: "Fatal Error compiling builtin function"
Date: Fri, 21 Jun 2019 12:33:14 +0200 [thread overview]
Message-ID: <20190621103314.-C54HIv_3B6gP9tc1xeX4XDNPENg5hGvuu6KDVuQwwA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-12595@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/issues/12595#issuecomment-504378577
Comment:
The bottom comment in the linked similar issue is probably what causes the crash.
We always have trouble with libraries and applications wanting to use huge portions of the stack for local data, yet failing to set their stack space requirements with `pthread_attr_setstacksize(3)` in their thread(s). This applies for Musl libc with its 80KiB default stack size, not glibc, which has a huge default stack size. As a consequence developers tend to don't care because of this.
qt5-webkit is old and most probably needs (a lot of?) patches to correctly define its requirements. If we are going to patch it that can only be guesswork and trial+error, with the main issue being to identify the places in the code where it should happen in the first place.
next prev parent reply other threads:[~2019-06-21 10:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 7:05 [ISSUE] " voidlinux-github
2019-06-21 10:33 ` voidlinux-github [this message]
2019-06-21 10:41 ` voidlinux-github
2019-06-21 10:44 ` voidlinux-github
2019-06-21 19:55 ` voidlinux-github
2019-06-21 20:23 ` voidlinux-github
2019-06-24 14:53 ` voidlinux-github
2019-06-24 14:54 ` voidlinux-github
2019-07-11 5:19 ` voidlinux-github
2019-07-18 19:37 ` voidlinux-github
2019-07-19 17:36 ` voidlinux-github
2019-07-20 19:36 ` [ISSUE] [CLOSED] " voidlinux-github
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=20190621103314.-C54HIv_3B6gP9tc1xeX4XDNPENg5hGvuu6KDVuQwwA@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).