On Wed, Jan 09, 2019 at 10:42:06PM +0100, Johannes Schauer wrote: > Quoting Faidon Liambotis (2019-01-09 16:16:40) > > > Until it is properly fixed upstream we can just temporarily disable > > > --enable-prof, right? > > We could, yes. This is a useful piece of functionality that I'd like to > > enable, though... > > but does it matter if proot disables it in its tests? > > I tried this in debian/rules: > > export MALLOC_CONF=prof:false > > according to what I read on http://jemalloc.net/jemalloc.3.html this should > disable --enable-prof at runtime, no? > > Unfortunately, the effect is the same and the testsuite never finishes but > gets > stuck on the jemalloc test.
Unfortunately, the initialization code runs regardless of whether prof was enabled or not, and from the code it seems like this is intentional... See here: https://github.com/jemalloc/jemalloc/blob/5.1.0/src/prof.c#L2392 ...where the relevant call to _Unwind_Backtrace is outside the "if (opt_prof) { }" block. (The code is similar in the dev branch) Regards, Faidon
