July 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] PetitParser in 3.0?

by Tudor Girba

It loads #development as any CI job should do. Doru On Fri, Jul 18, 2014 at 1:40 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Stephan Eggermont wrote > > And there is a image build at > > https://ci.inria.fr/pharo-contribution/job/PetitParser/ > > Interesting. I wonder what the ci is loading, because if I try to load the > default group in Pharo 3.0, I get an error (hence I load 'Core' and have no > problems) > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

July 18, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by Andres Valloud

I worked on that switch before, and IIRC it's just a linker switch that marks executables a certain way. So, if you have imagecfg.exe handy... http://support.microsoft.com/kb/297812 On 7/17/14 19:25 , Oscar E. A. CallaÃº wrote: > Well. It seems that Pharo vms must be compiled with that option :/ > > Cheers > > > On Wed, Jul 16, 2014 at 8:44 PM, <btc(a)openinworld.com > <mailto:btc@openinworld.com>> wrote: > > __ > Eliot Miranda wrote: >> >> >> >> On Wed, Jul 16, 2014 at 2:21 PM, Oscar E. A. CallaÃº >> <oscar.apollo(a)gmail.com <mailto:oscar.apollo@gmail.com>> wrote: >> >> Hi, >> >> I'm using Windows 8.1 (update1) 64bits with 4GB of physical >> RAM. I only need 1.5GB of RAM, so I think I don't need to >> configure my OS to take /3GB of RAM. >> >> >> Well my experience (and others) is that one can't grow the heap >> much above 1.1 Gb without using the /3Gb switch on Windows XP. I >> can't talk for 8.1. But if 8.x also limits memory to 2Gb/process >> unless the /3Gb switch is in effect then yes, you'll need to use >> the /3Gb switch. >> >> HTH >> Eliot >> >> >> Cheers >> >> On Wednesday, July 16, 2014, Eliot Miranda wrote: >> >> Hi Oscar, >> >> >> On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº >> <oscar.apollo(a)gmail.com> wrote: >> >> Hi guys, >> >> I'm running some experiments in Pharo. My data >> is aprox. 1.3GB. When I load my image on Mac, >> everything works perfectly. But, when I try to load >> the same image on Windows, I get this error: >> >> Unable to commit memory (1326649344 bytes requested) >> >> I tried the Pharo VM, cogMT and NBcog with and >> without the option >> >> AddressSpaceLimit = 2048 >> >> in the ini file >> >> Please help. >> >> What OS are you using? Have you read e.g. >> http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959(v=vs.85).… >> <http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959%28v=vs.85…>? >> >> > > Here are some additional links... > > /LARGEADDRESSAWARE (Handle Large Addresses) > http://msdn.microsoft.com/en-us/library/wz223b1z.aspx > > Memory Limits for Windows and Windows Server Releases > http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).a… > I learnt something new reading this article. For Win 8.1 64-bit, the > /3GB switch is not applicable or required. However the > /LARGEADDRESSAWARE linker option is critical for both 32-bit and > 64-bit VMs. Its only the default setting that changes between > compiling 32-bit or 64-bit applications. Some extracts... > > Limits on memory and address space depend on whether the > IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure > and 4-gigabyte tuning (4GT) are in use. > IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the > /LARGEADDRESSAWARE linker option. 4-gigabyte tuning (4GT), also > known as application memory tuning, or the /3GB switch, is a > technology (**only applicable to 32 bit systems**) that alters the > amount of virtual address space available to user mode applications. > > On x64-bit MS Windows, User-Mode virtual address space for each > 32-bit process > 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set > 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) > > On x64-bit MS Windows, User-Mode virtual address space for each > 64-bit process > 8 TB With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): > 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared > > cheers -ben > >> >> -- >> best, >> Eliot >> >> >> >> >> -- >> best, >> Eliot > >

July 18, 2014

Re: [Pharo-dev] Memory limit problems on Windows VM

by Oscar E. A. CallaÃº

Well. It seems that Pharo vms must be compiled with that option :/ Cheers On Wed, Jul 16, 2014 at 8:44 PM, <btc(a)openinworld.com> wrote: > Eliot Miranda wrote: > > > > > On Wed, Jul 16, 2014 at 2:21 PM, Oscar E. A. CallaÃº < > oscar.apollo(a)gmail.com> wrote: > >> Hi, >> >> I'm using Windows 8.1 (update1) 64bits with 4GB of physical RAM. I only >> need 1.5GB of RAM, so I think I don't need to configure my OS to take /3GB >> of RAM. >> > > Well my experience (and others) is that one can't grow the heap much > above 1.1 Gb without using the /3Gb switch on Windows XP. I can't talk for > 8.1. But if 8.x also limits memory to 2Gb/process unless the /3Gb switch > is in effect then yes, you'll need to use the /3Gb switch. > > > HTH > Eliot > > >> Cheers >> >> On Wednesday, July 16, 2014, Eliot Miranda wrote: >> >>> Hi Oscar, >>> >>> >>> On Wed, Jul 16, 2014 at 9:11 AM, Oscar E. A. CallaÃº < >>> oscar.apollo(a)gmail.com> wrote: >>> >>>> Hi guys, >>>> >>>> I'm running some experiments in Pharo. My data is aprox. >>>> 1.3GB. When I load my image on Mac, everything works perfectly. But, when I >>>> try to load the same image on Windows, I get this error: >>>> >>>> Unable to commit memory (1326649344 bytes requested) >>>> >>>> I tried the Pharo VM, cogMT and NBcog with and without the option >>>> >>>> AddressSpaceLimit = 2048 >>>> >>>> in the ini file >>>> >>>> Please help. >>>> >>> >>> What OS are you using? Have you read e.g. >>> http://msdn.microsoft.com/en-us/library/windows/hardware/dn613959(v=vs.85).… >>> >>> >> > Here are some additional links... > > /LARGEADDRESSAWARE (Handle Large Addresses) > http://msdn.microsoft.com/en-us/library/wz223b1z.aspx > > Memory Limits for Windows and Windows Server Releases > > http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).a… > I learnt something new reading this article. For Win 8.1 64-bit, the /3GB > switch is not applicable or required. However the /LARGEADDRESSAWARE > linker option is critical for both 32-bit and 64-bit VMs. Its only the > default setting that changes between compiling 32-bit or 64-bit > applications. Some extracts... > > Limits on memory and address space depend on whether the > IMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and > 4-gigabyte tuning (4GT) are in use. IMAGE_FILE_LARGE_ADDRESS_AWARE is set > or cleared by using the /LARGEADDRESSAWARE linker option. 4-gigabyte > tuning (4GT), also known as application memory tuning, or the /3GB switch, > is a technology (**only applicable to 32 bit systems**) that alters the > amount of virtual address space available to user mode applications. > > On x64-bit MS Windows, User-Mode virtual address space for each 32-bit > process > 4 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE set > 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared (default) > > On x64-bit MS Windows, User-Mode virtual address space for each 64-bit > process > 8 TB With IMAGE_FILE_LARGE_ADDRESS_AWARE set (default): > 2 GB with IMAGE_FILE_LARGE_ADDRESS_AWARE cleared > > cheers -ben > > >>> -- >>> best, >>> Eliot >>> >> > > > -- > best, > Eliot > > >

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Martin McClure

On 07/17/2014 04:37 PM, Sean P. DeNigris wrote: > Martin McClure-2 wrote >> Anyone using PetitParser in Pharo 3.0? > > Yes! > > 1. Open the Config Browser from the World menu > 2. Right click in the list pane and switch to the ss3 meta repo > 3. Load the PP config > 4. ConfigurationOfPetitParser project stableVersion load: 'Core' > > HTH Thanks a bunch, Sean! That loads in the latest 3.0 image, and the test pass. I gather that the GUI tools have not been ported forward? Regards, -Martin

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

MetaRepoForPharo20 does not necessarily contain versions that work for Pharo 3 (or 4). You might want to compare versions. Can't do it from here, as smalltalkhub crashes safari on iOS devices. Stephan

July 18, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Sean P. DeNigris

Stephan Eggermont wrote > And there is a image build at > https://ci.inria.fr/pharo-contribution/job/PetitParser/ Interesting. I wonder what the ci is loading, because if I try to load the default group in Pharo 3.0, I get an error (hence I load 'Core' and have no problems) ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768407.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Stephan Eggermont

On smalltalkhub, Moose/PetitParser And there is a image build at https://ci.inria.fr/pharo-contribution/job/PetitParser/ Stephan

July 17, 2014

Re: [Pharo-dev] PetitParser in 3.0?

by Sean P. DeNigris

Martin McClure-2 wrote > Anyone using PetitParser in Pharo 3.0? Yes! 1. Open the Config Browser from the World menu 2. Right click in the list pane and switch to the ss3 meta repo 3. Load the PP config 4. ConfigurationOfPetitParser project stableVersion load: 'Core' HTH ----- Cheers, Sean -- View this message in context: http://forum.world.st/PetitParser-in-3-0-tp4768398p4768405.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] SmalltalkHub and public write access

by Sean P. DeNigris

Nicolas Petton wrote > It should be working fine now. Thanks! That's important for contributions :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/SmalltalkHub-and-public-write-access-tp4768266p476840… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014

Re: [Pharo-dev] Logic we will have to clean

by Sean P. DeNigris

Why? Looks perfectly understandable to me ;-P ----- Cheers, Sean -- View this message in context: http://forum.world.st/Logic-we-will-have-to-clean-tp4768190p4768403.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 17, 2014