Control: tags -1 + moreinfo
Hallo James Henried,
was just looking through some random bug reports.
Maybe you could install the package systemd-coredump.
That way in the journal would appear a backtrace that
could give some hints where the segmentation fault happens.
Visible in the output of:
journalctl --no-pager
Additional you could install the package gdb and start
usbmuxd with the following command:
script -a ~/gdb-usbmuxd_$(date +%Y-%m-%d_%H-%M-%S).log -c "gdb -q -ex 'set
width 0' -ex 'set pagination off' -ex 'run' -ex 'info reg' -ex 'display/i \$pc'
-ex 'bt' -ex 'info share' -ex 'bt full' -ex detach -ex quit --args usbmuxd"
That should generate a file with a better backtrace of
the crashing process that you may forward to this bug report.
Even better would be if before running this you install
some debug symbol packages like described in following link:
https://wiki.debian.org/HowToGetABacktrace#Installing_the_debugging_symbols
In your case the package usbmuxd-dbgsym would be the first,
maybe others get requested when a first backtrace is received.
Kind regards,
Bernhard
