- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] pharo64+load code=broken image

by Eliot Miranda

Hi Javier, what does the crash.dmp file say? Or what does a gdb stacktrace say? _,,,^..^,,,_ (phone) > On Mar 23, 2018, at 7:18 AM, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > > no luck with this one :( > >> On Fri, Mar 23, 2018 at 4:48 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> Hi Javier, >> >> On 23 March 2018 at 04:54, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: >> > Hi folks, I take a fresh Pharo6.1 (spur64), load a git repository and save >> > the image. When reopening I get a segmentation fault. OS is ubuntu 17.04/64 >> > bits. I just cannot make it work, tried with all the vms I could (vmI61, >> > vmT61, vmLatest70, vmTLatest70). I suspect it is related to using git but >> > I'm not even sure. >> > >> > Below I put the involved code, crash dump at the end (seems to be the same >> > with any vm). btw, the vmILatest70 script does not seem to work (curl >> > https://get.pharo.org/64/vmILatest70 | bash). >> > >> > Any ideas? >> >> I'm using the following VM on Ubuntu 16.04 without any issues: >> >> http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… >> >> >> HTH, >> Alistair >> > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires

March 23, 2018

Re: [Pharo-dev] pharo64+load code=broken image

by Javier PimÃ¡s

no luck with this one :( On Fri, Mar 23, 2018 at 4:48 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > Hi Javier, > > On 23 March 2018 at 04:54, Javier PimÃ¡s <elpochodelagente(a)gmail.com> > wrote: > > Hi folks, I take a fresh Pharo6.1 (spur64), load a git repository and > save > > the image. When reopening I get a segmentation fault. OS is ubuntu > 17.04/64 > > bits. I just cannot make it work, tried with all the vms I could (vmI61, > > vmT61, vmLatest70, vmTLatest70). I suspect it is related to using git but > > I'm not even sure. > > > > Below I put the involved code, crash dump at the end (seems to be the > same > > with any vm). btw, the vmILatest70 script does not seem to work (curl > > https://get.pharo.org/64/vmILatest70 | bash). > > > > Any ideas? > > I'm using the following VM on Ubuntu 16.04 without any issues: > > http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded- > 201803160215-43a2f5c.zip > > > HTH, > Alistair > > -- Javier PimÃ¡s Ciudad de Buenos Aires

March 23, 2018

Re: [Pharo-dev] PharoDays: 14/15 June 2018

by Stephan Eggermont

Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi All > > We would like to organise PharoDays the 14 and 15 June. Could you tell us > if you see big problems from your side before we announce it. Works better than 7/8, which I cannot make Stephan Eggermont

March 23, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by CÃ©drick BÃ©ler

Thx Ben for all. I will investigate further as most of the students use windows (still I ask them top bring their computer cause here itâs all virtualized windows with network user files mounted on the virtual system launch). > > btw, what is the directory here that its trying to write to? I donât knowâ¦ I ask the student to send me the stack. I wonât see them until 2 weeks. But I will then try with some to make this stuff work more reliably and give/ask feedback here. Anyway, I still have the solution to launch the old way. So there is an alternative. But I really like the launcher. It really helps organizing (for me :)). For students, in a first approcach itâs not that important. > > > Now I notice... > the Linux PharoLauncher download is a ZIP file > and the Mac PharoLauncher download is a ZIP file > so... can we make the Windows PharoLauncher download a ZIP file? > > Doing that, at least as an interim measure, would *immediately* make PharoLauncher > usable to students on locked-down Windows machines in University student labs. > I'd expect this will improve the success with this experiment > to use PharoLauncher as the main user entry point. > > The problem with using an "Installer" for the Windows PharoLauncher is the large amount > of testing required to work *reliably* with *all* the "different ways people work" > under several different versions of Windows introduced different layers of user security intricacies. Oh yeahâ¦ I can see thatâ¦ and since I donât use windows since XP, I can tell you itâs a pain to just use it again. I (sadly) need a windows box to test. Iâm thinking also to prepare a linux virtual box image which is also interesting. But still, to get adoption (even for A or 2 student), its important that it works well on windows. Iâll give feedback (but in 2/3 weeks). Cheers, CÃ©drick > Lets move forward in small steps. A ZIP download/extract is simple, and consistent with other platforms. > > > In the meantime while waiting for that to happen, you can... > > 1. Download/extract http://files.pharo.org/platform/Pharo6.1-win.zip <http://files.pharo.org/platform/Pharo6.1-win.zip> > > 2. Rename Pharo6.1 folder to PharoLauncher > Rename Pharo6.1.* files to PharoLauncher1.1.* > > 3. Metacello new > smalltalkhubUser: 'Pharo' > project: 'PharoLauncher'; > configuration: 'PharoLauncher'; > load. > PhLDeploymentScript doAll. > PharoLauncher open. > Smalltalk snapshot: true andQuit: true. > > 4. Zip up the parent folder, test on another machine and provide a link to your students. > > cheers -ben > > > P.S. I was going to suggest also renaming Pharo.exe to PharoLauncher.exe > but with an empty Documents\Pharo\vms > I get... "Error: Cannot detect Pharo executable in C:\Temp\MyPharoLauncher\PharoLauncher" > in PhLVirtualMachine>>initializeOn: "File @ C:\Temp\MyPharoLauncher\PharoLauncher" > since "executables := aFolder allChildrenMatching: self class executableName." > is empty since "self class executableName" ==> "Pharo.exe" > > It would be nice for that to not be hard coded. I tried digging further but ran out of time. > I am curious it mattered since using "Pharo.exe" the Launcher went on to download a VM anyway. > > > P.S.2. > I believe the best path forward for system-wide PharoLauncher installed under "C:\Program Files" > would be to install there only... > * the VM > * PharoLauncher.ZIP > * a tiny non-Pharo wrapper program as the shortcut linked from AllUsers > Start Menu > PharoLauncher > that extracts PharoLauncher.ZIP to the user's data area and then starts that user specific PharoLauncher. > > Then regardless whether: > * they individually download/extract PharoLauncher.ZIP > * the system-wide-wrapper extracts PharoLauncher.ZIP > its a similar experience for users which should aid reliability by reducing the number of "different " use cases.

March 23, 2018

Re: [Pharo-dev] PharoDays: 14/15 June 2018

by Tudor Girba

Hi, Unfortunately, those dates do not work well for me. it would be hard for me to get there on those days. Cheers, Doru > On Mar 23, 2018, at 11:21 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > Hi All > > We would like to organise PharoDays the 14 and 15 June. Could you tell us > if you see big problems from your side before we announce it. > > Tx > -- www.tudorgirba.com www.feenk.com "It's not how it is, it is how we see it."

March 23, 2018

PharoDays: 14/15 June 2018

by Stephane Ducasse

Hi All We would like to organise PharoDays the 14 and 15 June. Could you tell us if you see big problems from your side before we announce it. Tx

March 23, 2018

Re: [Pharo-dev] pharo64+load code=broken image

by Alistair Grant

Hi Javier, On 23 March 2018 at 04:54, Javier PimÃ¡s <elpochodelagente(a)gmail.com> wrote: > Hi folks, I take a fresh Pharo6.1 (spur64), load a git repository and save > the image. When reopening I get a segmentation fault. OS is ubuntu 17.04/64 > bits. I just cannot make it work, tried with all the vms I could (vmI61, > vmT61, vmLatest70, vmTLatest70). I suspect it is related to using git but > I'm not even sure. > > Below I put the involved code, crash dump at the end (seems to be the same > with any vm). btw, the vmILatest70 script does not seem to work (curl > https://get.pharo.org/64/vmILatest70 | bash). > > Any ideas? I'm using the following VM on Ubuntu 16.04 without any issues: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… HTH, Alistair

March 23, 2018

[Pharo 7.0-dev] Build #717: 21640 Fix comment expressions in Number quo:

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #717 was: SUCCESS. The Pull Request #1146 was integrated: "21640 Fix comment expressions in Number quo:" Pull request url: https://github.com/pharo-project/pharo/pull/1146 Issue Url: https://pharo.fogbugz.com/f/cases/21640 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 23, 2018

pharo64+load code=broken image

by Javier PimÃ¡s

Hi folks, I take a fresh Pharo6.1 (spur64), load a git repository and save the image. When reopening I get a segmentation fault. OS is ubuntu 17.04/64 bits. I just cannot make it work, tried with all the vms I could (vmI61, vmT61, vmLatest70, vmTLatest70). I suspect it is related to using git but I'm not even sure. Below I put the involved code, crash dump at the end (seems to be the same with any vm). btw, the vmILatest70 script does not seem to work (curl https://get.pharo.org/64/vmILatest70 | bash). Any ideas? --- cli /CogNOS/image (master)$ ../vms/vmI61/pharo-ui Pharo.image ../scripts/loadSqueakNOSImage.st /CogNOS/image (master)$ ../vms/vmI61/pharo-ui SqueakNOS.image --- loadSqueaNOSImage.st Author useAuthor: 'LoadSqueakNOS' during: [ Metacello new baseline: #SqueakNOS; repository: 'github://nopsys/CogNOS/Image-src'; load ]. (Smalltalk saveAs: 'SqueakNOS') ifFalse: [ Smalltalk snapshot: false andQuit: true ]. /CogNOS/image (master)$ ../vms/vmI61/pharo-ui Pharo.image ../scripts/loadSqueakNOSImage.st /CogNOS/image (master)$ ../vms/vmI61/pharo-ui SqueakNOS.image ----- Segmentation fault Thu Mar 22 22:52:28 2018 /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo Pharo VM version: 5.0-201708271955 Sun Aug 27 20:00:28 UTC 2017 gcc 4.6.3 [Production Spur 64-bit ITHB VM] Built from: CoInterpreter VMMaker.oscog-eem.2265 uuid: 76b62109-629a-4c39-9641-67b53321df9a Aug 27 2017 With: StackToRegisterMappingCogit VMMaker.oscog-eem.2262 uuid: 8b531242-de02-48aa-b418-8d2dde0bec6c Aug 27 2017 Revision: VM: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Sun Aug 27 21:55:26 2017 +0200 $ Plugins: 201708271955 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Build host: Linux testing-gce-643eb2a1-aa49-4136-af37-2965c12a9e8f 3.13.0-115-generic #162~precise1-Ubuntu SMP Fri Mar 24 16:47:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux plugin path: /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955 [default: /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/] C stack backtrace & registers: rax 0xa6bdac40 rbx 0xa6bdaad0 rcx 0xa6bdacf8 rdx 0xa6bdab88 rdi 0xa6bda8a8 rsi 0xa6bda8a8 rbp 0xa6bdaa18 rsp 0xa6bdadb0 r8 0xa6bda2e8 r9 0xa6bda3a0 r10 0xa6bda458 r11 0xa6bda510 r12 0xa6bda5c8 r13 0xa6bda680 r14 0xa6bda738 r15 0xa6bda7f0 rip 0xa6bdae68 *[0x7ffea6bdae68] /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo[0x41cd91] /CogNOS/vms/vmI61/pharo-vm/lib/pharo/5.0-201708271955/pharo[0x41d11f] /lib/x86_64-linux-gnu/libc.so.6(+0x357f0)[0x7efdaadb67f0] /lib/x86_64-linux-gnu/libc.so.6(malloc_usable_size+0x12)[0x7efdaae08902] /usr/lib/nvidia-384/libGL.so.1(+0xba159)[0x7efdaa38b159] [0x7ffea6bd9116] Smalltalk stack dump: 0x7ffea6bea5e8 M ExternalAddress>finalize 0x64e4e90: a(n) ExternalAddress 0x7ffea6bea620 M WeakFinalizerItem>finalizeValues 0x64e37d8: a(n) WeakFinalizerItem 0x7ffea6bea658 M [] in WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea688 M BlockClosure>on:do: 0x2b643c0: a(n) BlockClosure 0x7ffea6bea6c8 M BlockClosure>on:fork: 0x2b643c0: a(n) BlockClosure 0x7ffea6bea708 M [] in WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea750 M OrderedCollection>do: 0x2b63b38: a(n) OrderedCollection 0x7ffea6bea7a0 M WeakRegistry>finalizeValues 0x347fb18: a(n) WeakRegistry 0x7ffea6bea7d8 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea808 M BlockClosure>on:do: 0x2b63a00: a(n) BlockClosure 0x7ffea6bea848 M BlockClosure>on:fork: 0x2b63a00: a(n) BlockClosure 0x7ffea6bea888 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea8d0 M WeakArray(SequenceableCollection)>do: 0x31fe7f0: a(n) WeakArray 0x7ffea6bea908 M [] in WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6bea948 M [] in Semaphore>critical: 0x6031ba0: a(n) Semaphore 0x7ffea6bea988 M BlockClosure>ensure: 0x2b5e260: a(n) BlockClosure 0x7ffea6bea9c8 M Semaphore>critical: 0x6031ba0: a(n) Semaphore 0x7ffea6beaa10 I WeakArray class>doOldFinalization 0x3498518: a(n) WeakArray class 0x7ffea6beaa60 I WeakArray class>finalizationProcess 0x3498518: a(n) WeakArray class 0x649cb58 s [] in WeakArray class>restartFinalizationProcess 0x6036d68 s [] in BlockClosure>newProcess Most recent primitives replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: at: stringHash:initialHash: stringHash:initialHash: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: stringHash:initialHash: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: at: stringHash:initialHash: stringHash:initialHash: stringHash:initialHash: tempAt: indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primGetPosition: replaceFrom:to:with:startingAt: shallowCopy replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: class **StackOverflow** **StackOverflow** indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: **StackOverflow** replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: **StackOverflow** indexOfAscii:inString:startingAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: replaceFrom:to:with:startingAt: replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: primWrite:from:startingAt:count: instVarAt: **StackOverflow** basicNew \\ \\ replaceFrom:to:with:startingAt: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: **StackOverflow** stringHash:initialHash: findFirstInString:inSet:startingAt: primWrite:from:startingAt:count: primGetPosition: **IncrementalGC** wait value wait value at: at: basicAt: at: at: expire at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: replaceFrom:to:with:startingAt: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: at: notNil notNil replaceFrom:to:with:startingAt: signal primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: primCloseNoError: wait primCloseNoError: signal wait signal wait signal wait signal wait replaceFrom:to:with:startingAt: signal size at: free stack page bytes 8192 available headroom 5576 minimum unused headroom 6032 (Segmentation fault) -- Javier PimÃ¡s Ciudad de Buenos Aires

March 23, 2018

Re: [Pharo-dev] Experiment: New Download page based on Pharo Launcher

by Ben Coman

On 23 March 2018 at 05:14, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > Hi, > > I just saw students and they still have some problem on windows with the > launcher. > > First, the launcher has to be run in admin mode. > > Then, the image download starts but there is an error when uncompressing. > Here is the stack. > > Any idea on how to fix that ? > > > > FileHandle>>streamError > FileHandle>>writeStream > FileSystem>>writeStreamOn: > FileReference>>writeStream > FileReference(AbstractFileReference)>>writeStreamDo: > ZipFileMember(ZipArchiveMember)>>extractInDirectory:overwrite: > btw, what is the directory here that its trying to write to? Now I notice... the Linux PharoLauncher download is a ZIP file and the Mac PharoLauncher download is a ZIP file so... can we make the Windows PharoLauncher download a ZIP file? Doing that, at least as an interim measure, would *immediately* make PharoLauncher usable to students on locked-down Windows machines in University student labs. I'd expect this will improve the success with this experiment to use PharoLauncher as the main user entry point. The problem with using an "Installer" for the Windows PharoLauncher is the large amount of testing required to work *reliably* with *all* the "different ways people work" under several different versions of Windows introduced different layers of user security intricacies. Lets move forward in small steps. A ZIP download/extract is simple, and consistent with other platforms. In the meantime while waiting for that to happen, you can... 1. Download/extract http://files.pharo.org/platform/Pharo6.1-win.zip 2. Rename Pharo6.1 folder to PharoLauncher Rename Pharo6.1.* files to PharoLauncher1.1.* 3. Metacello new smalltalkhubUser: 'Pharo' project: 'PharoLauncher'; configuration: 'PharoLauncher'; load. PhLDeploymentScript doAll. PharoLauncher open. Smalltalk snapshot: true andQuit: true. 4. Zip up the parent folder, test on another machine and provide a link to your students. cheers -ben P.S. I was going to suggest also renaming Pharo.exe to PharoLauncher.exe but with an empty Documents\Pharo\vms I get... "Error: Cannot detect Pharo executable in C:\Temp\MyPharoLauncher\PharoLauncher" in PhLVirtualMachine>>initializeOn: "File @ C:\Temp\MyPharoLauncher\PharoLauncher" since "executables := aFolder allChildrenMatching: self class executableName." is empty since "self class executableName" ==> "Pharo.exe" It would be nice for that to not be hard coded. I tried digging further but ran out of time. I am curious it mattered since using "Pharo.exe" the Launcher went on to download a VM anyway. P.S.2. I believe the best path forward for system-wide PharoLauncher installed under "C:\Program Files" would be to install there only... * the VM * PharoLauncher.ZIP * a tiny non-Pharo wrapper program as the shortcut linked from AllUsers > Start Menu > PharoLauncher that extracts PharoLauncher.ZIP to the user's data area and then starts that user specific PharoLauncher. Then regardless whether: * they individually download/extract PharoLauncher.ZIP * the system-wide-wrapper extracts PharoLauncher.ZIP its a similar experience for users which should aid reliability by reducing the number of "different " use cases.

March 23, 2018