Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-27 Thread Johannes Schauer
Hi Piotr and Faidon, On Thu, 10 Jan 2019 18:31:01 +0100 Johannes Schauer wrote: > Quoting Faidon Liambotis (2019-01-10 15:29:59) > > Unfortunately, the initialization code runs regardless of whether prof was > > enabled or not, and from the code it seems like this is intentional... > > > > See h

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-10 Thread Johannes Schauer
Hi Faidon, Quoting Faidon Liambotis (2019-01-10 15:29:59) > 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 > ...whe

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-10 Thread Faidon Liambotis
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 > > en

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Johannes Schauer
Hi Faidon, 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

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Faidon Liambotis
On Wed, Jan 09, 2019 at 11:23:19AM +0100, Johannes Schauer wrote: > Maybe you can report this directly to upstream? I thought of that, but then I saw that upstream is Piotr, who is also listed as a Maintainer of this package. Is that not the case? > Until it is properly fixed upstream we can just

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Johannes Schauer
Hi Faidon, Quoting Faidon Liambotis (2019-01-09 16:16:40) > On Wed, Jan 09, 2019 at 11:23:19AM +0100, Johannes Schauer wrote: > > Maybe you can report this directly to upstream? > I thought of that, but then I saw that upstream is Piotr, who is also listed > as a Maintainer of this package. Is tha

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-09 Thread Johannes Schauer
Hi, On Wed, 9 Jan 2019 00:27:03 +0200 Faidon Liambotis wrote: > So jemalloc 5.1.0-2 was recently uploaded to unstable. The build currently > fails due to the explicit dependency on libjemalloc1 (cf. #918741), but as > soon as this gets fixed, another issue is uncovered: > > While building this

Bug#918742: Initialization loop/deadlock when used with jemalloc

2019-01-08 Thread Faidon Liambotis
Package: src:fakechroot Version: 2.19-3 Severity: serious Hi again, So jemalloc 5.1.0-2 was recently uploaded to unstable. The build currently fails due to the explicit dependency on libjemalloc1 (cf. #918741), but as soon as this gets fixed, another issue is uncovered: While building this packa