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
On Jul 21, 2009, at 18:47 , Schwab,Wilhelm K wrote:
> Again, I *think* the problem is too much code removed, and failure
> to protect with #useOldNetwork. It blows up on IPv4; it happens
> both on Windows and Linux. If anyone has counter examples or can
> otherwise show me wrong, please set me straight.
>
> Bill
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]
> ] On Behalf Of Damien Cassou
> Sent: Tuesday, July 21, 2009 11:29 AM
> To: [email protected]
> Subject: Re: [Pharo-project] Show stopper network bug on Windows
>
> On Tue, Jul 21, 2009 at 12:56 PM, Adrian Lienhard<[email protected]>
> wrote:
>> If this bug also exists in Squeak (which I expect since it seems a VM
>> problem), I suggest to report it there too (and create a Mantis
>> entry).
>
> No, it's only Pharo.
>
> --
> Damien Cassou
> http://damiencassou.seasidehosting.st
>
> "Lambdas are relegated to relative obscurity until Java makes them
> popular by not having them." James Iry
>
> _______________________________________________
> 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
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
