Re: [racket-dev] Creating executables still broken

2011-10-04 Thread Marijn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/03/11 17:07, Matthew Flatt wrote: > At Mon, 03 Oct 2011 16:10:15 +0200, Marijn wrote: >> creating executables is still broken and seems now to cause lots >> of memory allocation causing my system to start thrashing... > > I've fixed the problem

Re: [racket-dev] Creating executables still broken

2011-10-04 Thread Matthew Flatt
I think I found the problem. Can you try the latest version? At Tue, 04 Oct 2011 09:42:53 +0200, Marijn wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 10/03/11 17:07, Matthew Flatt wrote: > > At Mon, 03 Oct 2011 16:10:15 +0200, Marijn wrote: > >> creating executables is still bro

[racket-dev] blocked on a mzrt-sema that gets collected: okay?

2011-10-04 Thread John Clements
I conjecture that if a place is blocked on a mzrt_sema semaphore and if that semaphore is then collected using a call to mzrt_sema_destroy(), then the waiting thread will simply wait forever. Is that correct? John smime.p7s Description: S/MIME cryptographic signature

Re: [racket-dev] blocked on a mzrt-sema that gets collected: okay?

2011-10-04 Thread Matthew Flatt
At Tue, 4 Oct 2011 13:34:17 -0700, John Clements wrote: > I conjecture that if a place is blocked on a mzrt_sema semaphore and if that > semaphore is then collected using a call to mzrt_sema_destroy(), then the > waiting thread will simply wait forever. Is that correct? Not necessarily; it may

Re: [racket-dev] blocked on a mzrt-sema that gets collected: okay?

2011-10-04 Thread John Clements
On Oct 4, 2011, at 1:48 PM, Matthew Flatt wrote: > At Tue, 4 Oct 2011 13:34:17 -0700, John Clements wrote: >> I conjecture that if a place is blocked on a mzrt_sema semaphore and if that >> semaphore is then collected using a call to mzrt_sema_destroy(), then the >> waiting thread will simply w