Github messages for voidlinux
 help / color / mirror / Atom feed
From: agausmann <agausmann@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Prusa-slicer segfault on start, x86_64-musl, probably wxwidgets related
Date: Tue, 17 Oct 2023 22:32:38 +0200	[thread overview]
Message-ID: <20231017203238.L82WIW11l2PN8FD8tlfI4MtGPNz5Bieozz3ke7vMAkI@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: 612 bytes --]

New comment by agausmann on void-packages repository

https://github.com/void-linux/void-packages/issues/46687#issuecomment-1767123255

Comment:
> Interestingly the dbg repo for x86_64-musl results in a prusa-slicer binary that has an exec format error on launch.

I think that's true for all dbg packages; they ship ELFs containing the debuginfo and not the machine code. Also partly evidenced by `interpreter *empty*`

Some tools like gdb will be able to locate the separate debuginfo file in `/usr/debug`. If the tool doesn't support that, you may be able to use `eu-unstrip` to recombine the two files


  parent reply	other threads:[~2023-10-17 20:32 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 [this message]
2023-10-20 13:31 ` alpaca-ninetynine
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=20231017203238.L82WIW11l2PN8FD8tlfI4MtGPNz5Bieozz3ke7vMAkI@z \
    --to=agausmann@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).