From: alpaca-ninetynine <alpaca-ninetynine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Prusa-slicer segfault on start, x86_64-musl, probably wxwidgets related
Date: Fri, 20 Oct 2023 15:31:11 +0200 [thread overview]
Message-ID: <20231020133111.WO8cpZC2iTkV4NYQsRfYtRxYzgtkDtRKT7-0BU8b08E@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46687@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
New comment by alpaca-ninetynine on void-packages repository
https://github.com/void-linux/void-packages/issues/46687#issuecomment-1772746651
Comment:
Adding a backtrace from my experience of the segfault in case it helps figuring out what's going on, though I guess the referenced function is in the patch above.
#0 0x00007ffff7d90ba5 in std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >::_M_assign(std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > const&) ()
from /usr/lib/libstdc++.so.6
#1 0x00007ffff4198dc6 in wxTranslations::SetLanguage(wxLanguage) () from /usr/lib/libwx_baseu-3.2.so.0
#2 0x0000555555e4165a in ?? ()
#3 0x0000555555e434e2 in ?? ()
#4 0x0000555555e45b26 in ?? ()
#5 0x00007ffff4148b23 in wxEntry(int&, wchar_t**) () from /usr/lib/libwx_baseu-3.2.so.0
#6 0x0000555555e2ccee in ?? ()
#7 0x0000555555837ee6 in ?? ()
#8 0x000055555581ce74 in main ()
next prev parent reply other threads:[~2023-10-20 13:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-15 6:32 [ISSUE] " Vaelatern
2023-10-16 8:52 ` sgn
2023-10-16 16:26 ` Vaelatern
2023-10-17 1:34 ` sgn
2023-10-17 1:48 ` Vaelatern
2023-10-17 1:57 ` Vaelatern
2023-10-17 20:30 ` agausmann
2023-10-17 20:32 ` agausmann
2023-10-17 20:32 ` agausmann
2023-10-17 20:32 ` agausmann
2023-10-20 13:31 ` alpaca-ninetynine [this message]
2023-10-20 17:37 ` Vaelatern
2024-02-19 7:58 ` kevcrumb
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=20231020133111.WO8cpZC2iTkV4NYQsRfYtRxYzgtkDtRKT7-0BU8b08E@z \
--to=alpaca-ninetynine@users.noreply.github.com \
--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).