Hello everyone,
are there any issues running 64 bit VisualWorks? Will it work ok under 64 bit Linux? thanks, David _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Yes, we run several vw7.6 64bit (debian linux) images.
But we still do all development with 32bit, because: - compiling code, can crash the image (especially when class def changes) - loading code from store, can crash the image But when a 64bit image it is eventually build (step by step & trail and error) and deployed, it keeps running our server app without any problems. greetings, Mathieu ps. In vw7.7 the 64bit support should be better, but we've no experience with it. On Fri, Feb 12, 2010 at 9:12 PM, David Long <[hidden email]> wrote: > Hello everyone, > > are there any issues running 64 bit VisualWorks? Will it work ok under 64 > bit Linux? > > thanks, > > David > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > -- AG5 Timorplein 37 1094 CC Amsterdam T 020 4630942 F 020 4630946 _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Yes, there were issues related to class creation and garbage
collection of obsolete classes that were fixed in 7.7, along with quite a
number of other issues.
At 05:05 AM 2010-02-15, Mathieu van Echtelt wrote: Yes, we run several vw7.6 64bit (debian linux) images. --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Mathieu van Echtelt-2
I believe the problems below have been addressed. The issue I know of
was that the IGC (incremental garbage collector) could collect classes from under existing instances in some cases. As a workaround, you can disable the IGC. The newer 7.8 VMs have the fix. -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of Mathieu van Echtelt Sent: Monday, February 15, 2010 2:05 AM To: David Long Cc: VW NC Subject: Re: [vwnc] 64 bit Visualworks? Yes, we run several vw7.6 64bit (debian linux) images. But we still do all development with 32bit, because: - compiling code, can crash the image (especially when class def changes) - loading code from store, can crash the image But when a 64bit image it is eventually build (step by step & trail and error) and deployed, it keeps running our server app without any problems. greetings, Mathieu ps. In vw7.7 the 64bit support should be better, but we've no experience with it. On Fri, Feb 12, 2010 at 9:12 PM, David Long <[hidden email]> wrote: > Hello everyone, > > are there any issues running 64 bit VisualWorks? Will it work ok under > 64 bit Linux? > > thanks, > > David > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > -- AG5 Timorplein 37 1094 CC Amsterdam T 020 4630942 F 020 4630946 _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Specifically, the scenario under which this can happen is as
follows. A new class is created and, while the garbage collector has not
yet reached the class table, adopts instances that already exist in old
space. This could happen if loading a new definition for a class, where
we create the definition as a new class, and then become: the old one.
The garbage collector then processes the class table, and we delete all
references to the new class. At that point the class should be kept,
because it has instances which point to it, but the fact that they point
to it has been lost.
However, for this to happen, we'd have to have a class, created as such, with instances, to which all references had been deleted, other than those from the instances. So it could not, for example, be a subclass of anything, because it would be listed in the subclasses instance variable of the parent class. At 02:14 PM 2010-02-16, Valloud, Andres wrote: I believe the problems below have been addressed. The issue I know of --
Alan Knight [|], Engineering Manager, Cincom Smalltalk
_______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
In reply to this post by Mathieu van Echtelt-2
Mathieu van Echtelt wrote:
> Yes, we run several vw7.6 64bit (debian linux) images. > > But we still do all development with 32bit, because: [...] > > ps. In vw7.7 the 64bit support should be better, but we've no > experience with it. We've done fairly extensive development and testing with 64-bit 7.6 and 7.7. 7.7 is *much* better than 7.6. We run on both Linux and Solaris, and have found no significant problems. Regards, -Martin _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Hi Martin,
thanks - this is good to know. I'm confident now that moving to 64 bit will work. thanks, David > Mathieu van Echtelt wrote: >> Yes, we run several vw7.6 64bit (debian linux) images. >> >> But we still do all development with 32bit, because: > > [...] > >> >> ps. In vw7.7 the 64bit support should be better, but we've no >> experience with it. > > We've done fairly extensive development and testing with 64-bit 7.6 and > 7.7. 7.7 is *much* better than 7.6. We run on both Linux and Solaris, > and have found no significant problems. > > Regards, > > -Martin > _______________________________________________ > vwnc mailing list > [hidden email] > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > _______________________________________________ vwnc mailing list [hidden email] http://lists.cs.uiuc.edu/mailman/listinfo/vwnc |
Free forum by Nabble | Edit this page |