control: forwarded -1 mocma...@daper.net * Milan P. Stanic <m...@arvanta.net> [2017-02-14 12:57 +0100]:
> Package: moc > Version: 1:2.6.0~svn-r2935-1 > Severity: normal > > Dear Maintainer, > > * What led up to the situation? > starting mocp from cli on aarch64, testing > > * What exactly did you do (or not do) that was effective (or > ineffective)? > mocp > > * What was the outcome of this action? > Segmentation fault > And here it is what dmesg says: This is a kernel crash trace. If you want to trigger moc's debugging symbols you have to install moc-dbgsym_2.6.0~svn-r2935-1_arm64.deb, but shouldn't be very meaningful. See [0] > [132723.218509] mocp[11584]: unhandled level 3 translation fault (11) > at 0x556fcb5000, esr 0x92000007 > [132723.218515] pgd = ffffffc056340000 > [132723.218522] [556fcb5000] *pgd=0000000096332003, > *pud=0000000096332003, *pmd=0000000119080003, > *pte=0000000000000000 > > [132723.218537] CPU: 3 PID: 11584 Comm: mocp Not tainted 3.18.0-5-oak #8 > [132723.218540] Hardware name: Mediatek Elm rev3 board (DT) Which hardware are you running Debian on? On a RasPi moc runs very well on all variants (1,2,3), though. Anyway, could you please run "mocp -D" and provide the mocp_client_log and mocp_server_log in a compressed tarball? You'll find these files in the dir where you fired up mocp. The crash can be caused by missing RAM, full filesystems, non writeable cachedir (/tmp?) etc. Maybe upstream has an idea on how to segfault moc. I never made it.... [0] http://debug.mirrors.debian.org/debian-debug/ Elimar -- .~. /V\ L I N U X /( )\ >Phear the Penguin< ^^-^^
