On Mon, May 09, 2016 at 08:21:34PM +0200, Jeremie Courreges-Anglas wrote: > Juan Francisco Cantero Hurtado <i...@juanfra.info> writes: > > > On Sun, May 08, 2016 at 12:13:20PM +0200, Jeremie Courreges-Anglas wrote: > >> Jeremie Courreges-Anglas <j...@wxcvbn.org> writes: > >> > >> > Juan Francisco Cantero Hurtado <i...@juanfra.info> writes: > >> > > >> >> On Tue, Apr 26, 2016 at 11:28:52PM +0200, Jeremie Courreges-Anglas > >> >> wrote: > >> >>> Amit Kulkarni <amitk...@gmail.com> writes: > >> >>> > >> >>> > This fell through the cracks. Can somebody please import it now that > >> >>> > ports > >> >>> > is unlocked? > >> >>> > >> >>> Importing it now would perhaps get more bug reports, but we already > >> >>> know > >> >>> that there were unsolved issues: > >> >>> > >> >>> >> > I've seeing a bunch of double-free and use-after-free in htop. > >> >>> >> > Please, > >> >>> >> > run your tests with "MALLOC_OPTIONS=CFGJU htop" and fix the code > >> >>> >> > yourself in the upstream github repo if you can. > >> >> > >> >> I've attached an updated port. Now it uses the "debug" target by > >> >> default, so you can get a backtrace with the symbols included to send a > >> >> better bug report to upstream. > >> > > >> > Looks like bugs have magically vanished. ok jca@ to import it, > >> > I suggest you keep the debug symbols for now. > >> > >> While I think about it, please set MODPY_RUNDEP=No, python is only used > >> at build time py MakeHeaders.py. > > > > I was not asking for OKs :P . > > Then what are you waiting for? :)
I'm just updating the tarball, so people doesn't test old code. > > > I think that htop is not ready yet. > > Software = bugs. More people who use it = more chances for someone to > hit a bug, send a report, find a fix, etc. I think you're being > conservative here. There are a bunch of random crashes waiting for a fix: https://github.com/hishamhm/htop/pull/398 -- Juan Francisco Cantero Hurtado http://juanfra.info
