El miércoles, 15 de febrero de 2017 20h'09:36 ART, Joseph Rushton Wakeling
<joseph.wakel...@webdrake.net> escribió:
On 11/02/17 17:31, Joseph Rushton Wakeling wrote:
I just reproduced the issue in a VirtualBox install of 14.04 to get these
details. Kernel report in kern.log:
Feb 11 17:16:19 vb1404 kernel: [ 534.781526] traps: gcc[6209] general
protection ip:7f6632d1b1ee sp:7fff0a09e2f0 error:0 in
libc-2.23.so[7f6632bd8000+1bf000]
And `dmesg | grep -i gcc` gave this output:
[ 0.000000] Linux version 4.4.0-62-generic
(buildd@lcy01-33) (gcc version
4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #83~14.04.1-Ubuntu SMP Wed Jan 18
18:10:30 UTC 2017 (Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40)
[ 534.781526] traps: gcc[6209] general protection ip:7f6632d1b1ee
sp:7fff0a09e2f0 error:0 in libc-2.23.so[7f6632bd8000+1bf000]
This may give enough information for someone to suggest the next step.
I'm not very experienced at interpreting these kinds of
messages, but if I
understand right they would suggest a libc compatibility issue ... ?
Folks, could I ping on the above?
It seems like a rather severe limitation on the universality of
the package (at
a minimum it probably restricts the package to working on
systems with the same
or later libc) so I'm curious if anyone has any thoughts on if
and how this
could be ameliorated.
I'll check your snap first thing once I am at a computer again. From
experience with classic confinement though, stage-packages to provide
runnables are most of the time the root cause. There was discusssion on
having ld set --library-path in be core snap to have called binaries not
reach out to the system and get confused.
Zygmunt, any update on that?
--
Enviado con Dekko desde mi dispositivo Ubuntu
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
