Re: [PATCH] Port leak when using clisp

2015-08-28 Thread Samuel Thibault
Samuel Thibault, le Fri 28 Aug 2015 01:37:07 +0200, a écrit : > Applied, thanks! I believe it fixed a few other packages in debian. Samuel

Re: [PATCH] Port leak when using clisp

2015-08-27 Thread Samuel Thibault
Hello, Applied, thanks! Samuel

Re: [PATCH] Port leak when using clisp

2015-08-27 Thread Flávio Cruz
I've split the patch into two. Cheers Flavio On Thu, 27 Aug 2015 at 11:53 Justus Winter < 4win...@informatik.uni-hamburg.de> wrote: > Hi, > > Quoting Flávio Cruz (2015-08-27 00:26:13) > > Em qua, 26 de ago de 2015 às 12:18, Justus Winter < > > 4win...@informatik.uni-hamburg.de> escreveu: > > > >

Re: [PATCH] Port leak when using clisp

2015-08-27 Thread Justus Winter
Quoting Flávio Cruz (2015-08-27 00:26:13) > I wrote: > Fwiw, I prefer inlined patches so I can reply easier ;) > > OK ;) Oh no, but the new patch got corrupted now :/ I should have suggested "git send-email", but didn't. Sorry about that... Justus

Re: [PATCH] Port leak when using clisp

2015-08-27 Thread Justus Winter
Hi, Quoting Flávio Cruz (2015-08-27 00:26:13) > Em qua, 26 de ago de 2015 às 12:18, Justus Winter < > 4win...@informatik.uni-hamburg.de> escreveu: > > > > After looking around and using KDB, I've figured out that the following > loop in > > kern/exceptions.c/exception_raise_continue_

Re: [PATCH] Port leak when using clisp

2015-08-26 Thread Flávio Cruz
Em qua, 26 de ago de 2015 às 12:18, Justus Winter < 4win...@informatik.uni-hamburg.de> escreveu: > > > After looking around and using KDB, I've figured out that the following > loop in > > kern/exceptions.c/exception_raise_continue_slow was the culprit: > > Could you elaborate a little on your met

Re: [PATCH] Port leak when using clisp

2015-08-26 Thread Justus Winter
Hi Flávio :) Quoting Flávio Cruz (2015-08-26 01:46:16) > Next, I started the bootstrapping process to compile SBCL but it would always > fail with a kernel panic since Mach was unable to allocate more slabs for the > ipc_port data structure. I figured out that the kernel had thousands of > inactiv