Github messages for voidlinux
 help / color / mirror / Atom feed
From: duncancmt <duncancmt@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: flatpak segfaults on remote-add on aarch64 musl
Date: Wed, 09 Sep 2020 18:28:19 +0200	[thread overview]
Message-ID: <20200909162819.FL66MVCRH8s_-dW_MaBYM7Ojn4B1jpdcgbaenGzPCkE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24783@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]

New comment by duncancmt on void-packages repository

https://github.com/void-linux/void-packages/issues/24783#issuecomment-689674628

Comment:
Thanks for the help. I have a coredump and all the `*-dbg` packages installed. However `gdb` _itself_ aborts when running `flatpak` or when analyzing the coredump:

```
$ gdb `which flatpak` core.12507
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "aarch64-linux-musl".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /bin/flatpak...
Reading symbols from /usr/lib/debug//usr/bin/flatpak...
[New LWP 12512]
[New LWP 12507]
[New LWP 12511]
[New LWP 12509]

warning: Can't read pathname for load map: No error information.
Core was generated by `/usr/bin/flatpak remote-add --if-not-exists flathub https://flathub.org/repo/fl'.
Program terminated with signal SIGSEGV, Segmentation fault.
Aborted
$ echo $?
134
```

  parent reply	other threads:[~2020-09-09 16:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 14:56 [ISSUE] flatpak segfaults on remote-add duncancmt
2020-09-09 14:58 ` flatpak segfaults on remote-add on aarch64 musl ericonr
2020-09-09 16:09 ` duncancmt
2020-09-09 16:21 ` ericonr
2020-09-09 16:28 ` duncancmt [this message]
2020-09-09 16:32 ` ericonr
2020-09-09 16:33 ` duncancmt
2020-09-09 18:13 ` duncancmt
2020-09-09 18:17 ` duncancmt
2020-09-09 18:18 ` ericonr
2020-09-09 18:19 ` ericonr
2020-09-09 18:34 ` duncancmt
2020-09-09 19:03 ` ericonr
2020-09-09 19:03 ` ericonr
2020-10-12  1:03 ` duncancmt
2020-10-12  1:03 ` [ISSUE] [CLOSED] " duncancmt

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=20200909162819.FL66MVCRH8s_-dW_MaBYM7Ojn4B1jpdcgbaenGzPCkE@z \
    --to=duncancmt@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).