Anyone understand what's going on here? Any program at all (even trivial ones) linked to tcmalloc crash during startup on ARM 32 bit.
https://bugzilla.redhat.com/show_bug.cgi?id=1312462
At Tom's recommendation, I have added a patch to dist-git that disables hardened build on 32 bit ARM builds of gperftools, but that's quite a big hammer, and neither of us understands the underlying problem very much.
Rich.
On Mon, Feb 29, 2016 at 01:41:20PM +0000, Richard W.M. Jones wrote:
Anyone understand what's going on here? Any program at all (even trivial ones) linked to tcmalloc crash during startup on ARM 32 bit.
https://bugzilla.redhat.com/show_bug.cgi?id=1312462
At Tom's recommendation, I have added a patch to dist-git that disables hardened build on 32 bit ARM builds of gperftools, but that's quite a big hammer, and neither of us understands the underlying problem very much.
Presumably the previous version 2.4 was working fine, so its something introduced between then and 2.4.90 that causes the breakage. Since you have a trivial reproducable test case, probably the easiest thing is to take upstream git and run a bisect across it with your test case.
Regards, Daniel
On Mon, Feb 29, 2016 at 01:51:22PM +0000, Daniel P. Berrange wrote:
On Mon, Feb 29, 2016 at 01:41:20PM +0000, Richard W.M. Jones wrote:
Anyone understand what's going on here? Any program at all (even trivial ones) linked to tcmalloc crash during startup on ARM 32 bit.
https://bugzilla.redhat.com/show_bug.cgi?id=1312462
At Tom's recommendation, I have added a patch to dist-git that disables hardened build on 32 bit ARM builds of gperftools, but that's quite a big hammer, and neither of us understands the underlying problem very much.
Presumably the previous version 2.4 was working fine, so its something introduced between then and 2.4.90 that causes the breakage. Since you have a trivial reproducable test case, probably the easiest thing is to take upstream git and run a bisect across it with your test case.
Very good point - I'll bisect it now.
Rich.
https://bugzilla.redhat.com/show_bug.cgi?id=1312462
After a very long trip round the houses, it seems as if it might be a glibc or linker problem. Maybe. In any case the upstream developer seems to think so.
Rich.
-
Daniel P. Berrange -
Richard W.M. Jones