I am hopefully getting that answer for us. Actually, it just blew up in 10264, but over #next returning nil in Monticello, or so it seems.
More fundamentally than that, are you saying that the code works on a mac, or is it that you have an IPv6-aware network? Again, I have seen this on both Windows and Linux, and strongly suspect that the problem is that #primHostNameSize blows up on IPv4 or otherwise in connection with trying to accommodate both IP standards. Bill -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stéphane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: [email protected] Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related. > In this case the first step woud be to identify which update > introduced the problem. > > Suppose that a core #10200 image still works, you could do: > > 10200 to: 10384 do: [ :i | > Utilities updateFromServerThroughUpdateNumber: i. > NetNameResolver localHostAddress ] > > And then see after which update number the first exception is thrown. > I did not test this, but it should work. > > Adrian _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
