Github messages for voidlinux
 help / color / Atom feed
Subject: [ISSUE] kodi-rpi segfaults on startup on rpi-musl (original 256M raspberrypi B)
Date: Sun, 10 Nov 2019 20:25:23 +0100
Message-ID: <> (raw)

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

New issue by oldlaptop on void-packages repository

<!-- Don't request update of package. We have a script for that. . However, a quality pull request may help. -->
### System

* xuname:  
Void 4.19.81_1 armv6l-musl  uptodate rFF
* package:  

### Expected behavior
kodi should probably at least start.

### Actual behavior
kodi segfaults on startup. The backtrace in the wrapper script's generated "crash log" is essentially worthless (available on request, anyhow); running gdb on the actual binary yields the following:
```$ gdb /usr/lib/kodi/kodi-rbpi 
GNU gdb (GDB) 8.3.1
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
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 "arm-linux-musleabihf".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/kodi/kodi-rbpi...
(No debugging symbols found in /usr/lib/kodi/kodi-rbpi)
(gdb) run
Starting program: /usr/lib/kodi/kodi-rbpi 

Program received signal SIGSEGV, Segmentation fault.
0xb6fb7c58 in do_relocs (dso=dso@entry=0xb6ffd6d0 <app>, rel=0x796fc4, rel_size=1463840, stride=3069935072, stride@entry=2) at ldso/dynlink.c:423
423     ldso/dynlink.c: No such file or directory.
(gdb) bt
#0  0xb6fb7c58 in do_relocs (dso=dso@entry=0xb6ffd6d0 <app>, rel=0x796fc4, rel_size=1463840, stride=3069935072, stride@entry=2) at ldso/dynlink.c:423
#1  0xb6fb8ccc in reloc_all (p=p@entry=0xb6ffd6d0 <app>) at ldso/dynlink.c:1327
#2  0xb6fba950 in __dls3 (sp=<optimized out>) at ldso/dynlink.c:1906
#3  0xb6fba298 in __dls2 (base=<optimized out>, sp=0xbefff8a0) at ldso/dynlink.c:1650
#4  0xb6fb7270 in _dlstart () from /lib/
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Following duncaen's suggestion on IRC the kodi-rbpi binary's stack size was increased with chelf first to 4M, and then to 8M (e.g. `# chelf -s $(dc -e '8192 1024 *p') /usr/lib/kodi/kodi-rbpi`), with no apparent effect.

### Steps to reproduce the behavior
Install kodi-rpi, try to run it.

                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Github messages for voidlinux

Archives are clonable: git clone --mirror

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone