Noa Resare wrote:
ons 2004-10-20 klockan 18:47 +0200 skrev Guilhem Lavaux:
I have now tested the new code a bit. I have succeeded to hang it once
after about 5 hours of testing (but that could be related to the problem
below) but it is much more stable than any other kaffe version I have
tested.
T
ons 2004-10-20 klockan 18:47 +0200 skrev Guilhem Lavaux:
> Noa Resare wrote:
> > ons 2004-10-20 klockan 08:00 +0200 skrev Guilhem Lavaux:
> >
> >>I have identified and patched a race vulnerability which happens at
> >>thread destruction and another one (thanks to helmer) which happens at
> >>thr
ons 2004-10-20 klockan 18:47 +0200 skrev Guilhem Lavaux:
>
> I've just commited it. Please test it extensively. I would like also a
> thread hog test to see if there are memory leaks with the new scheme.
>
> Cheers,
>
> Guilhem.
I have now tested the new code a bit. I have succeeded to hang i
Noa Resare wrote:
ons 2004-10-20 klockan 18:47 +0200 skrev Guilhem Lavaux:
Hi Noa,
I've just commited it. Please test it extensively. I would like also a
thread hog test to see if there are memory leaks with the new scheme.
Cheers,
Guilhem.
After half an hour of testing here it looks much better
ons 2004-10-20 klockan 18:47 +0200 skrev Guilhem Lavaux:
>
> Hi Noa,
>
> I've just commited it. Please test it extensively. I would like also a
> thread hog test to see if there are memory leaks with the new scheme.
>
> Cheers,
>
> Guilhem.
After half an hour of testing here it looks much bet
Noa Resare wrote:
ons 2004-10-20 klockan 08:00 +0200 skrev Guilhem Lavaux:
I have identified and patched a race vulnerability which happens at
thread destruction and another one (thanks to helmer) which happens at
thread creation. I'll try to commit it this evening.
Thanks for looking for the pr
ons 2004-10-20 klockan 08:00 +0200 skrev Guilhem Lavaux:
>
> I have identified and patched a race vulnerability which happens at
> thread destruction and another one (thanks to helmer) which happens at
> thread creation. I'll try to commit it this evening.
>
> Thanks for looking for the problem
Noa Resare wrote:
Hello
Now I'm back from a few days away visiting my parents and I have
continued my investigation on the pthread instability in kaffe.
What I have concluded is sadly not what I had hoped for. I was looking
for a change in the pthread code somewhere between today and 1.1.4 that
int
Hello
Now I'm back from a few days away visiting my parents and I have
continued my investigation on the pthread instability in kaffe.
What I have concluded is sadly not what I had hoped for. I was looking
for a change in the pthread code somewhere between today and 1.1.4 that
introduced the lock