[kris]

... and you can get it here: http://svn.dsource.org/svn/projects/mango/downloads/

As usual, the changes are noted in the readme.txt file. Here's some highlights:

- a few bugs fixed
- mango.cluster has filled out considerably, attributable to old age. It needs a howto document though
- ICacheEntry had to change its name to IPayload to play nicely with mango.cluster (hope that's not a major inconvenience)

- Kris

[JJR]

I downloaded the update from svn. Here's an odd error. Cluster.d uses msleep(). Oddly, Linux doesn't appear to have this C function although phobos defines it in std.c.time for all platforms. Apparantly Linux only has usleep() (microsecond based), so I guess that will have to used instead of msleep in Cluster.d.

This is a phobos error then.

I assume usleep(500000) should replace msleep(500) on Linux then.

[kris]

Thanks John. I'll change it to usleep (500_000) ...

Other than that, are there any compile problems?

[JJR]

You're not going to like this, Kris. It segfaults in the same spot as before when testing testMulticast()... and that's even though it doesn't have the invalid "break."

And it appears to be the same gc corruption problem (mark).

Alas, the pain is not complete...

[kris]

[JJR]

It seems that the (quit || Socket.isCancelled()) branch is never being taken; therefore, lives is never set to 0. Kind of strange.

As a result, the while loop is iterating twice and getting hung up after the second reader.read(buffer);

Here's a sample of the output:

[kris]

[kris]

Glad to see the log timestamp is looking more reasonable

[JJR]

[kris]

So, where in the sequence does the static destructor get invoked? Is it after the "mango.unittest - Done" and before the segfault?

Good question about the lifespan of the static Socket.cancelled ... I had just assumed it was the equivalent of checking a global variable, but then the Socket.isCancelled() is a static method call on a module that should have gone through its static destructor already. I wonder if there's some bogosity in doing that?

To answer the question, I added a global-scope method isDone() along with a 'done' bool to Socket.d, where the latter is set by the destructor also. Now it looks just like a C method ... then checked the generated code to see if there was any difference in how the two methods (isDone & isCancelled) interact with their environment and how the caller invokes them. From that I can say that a static method residing within a class is treated (from an execution standpoint) exactly the same way as a global method is; there's no noticeable difference in this test. That does not mean it's the same under linux, but it's very likely to be the case.

Just to be sure we're not on another wild-goose chase, if you comment out the testMulticast() line

[JJR]

[JJR]

I'm going to be away for several hours. I got called out to work.

Will check in to the forum when I get back....

[kris]

... and my dsl modem apparently died right after my last post (this is dialup). Will get back online in a few days.

- Kris

[JJR]

Ugh... my little callout to work turned into 16.8 hours of work straight! That's one of the longest jaunts I've done in awhile.

Kris, you're on a modem again? Ouch, how will you survive? I borrowed my folks dialup connection once while visiting them -- the speed (or lack thereof) was almost unbearable. I almost had to start playing the "Blue Danube" to get into the right mood!

Take away my DSL,and I'd probably start twitching from withdrawel.

[kris]