September 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo web page download button

by Marcus Denker

On Sep 23, 2011, at 9:47 PM, Noury Bouraqadi wrote: > Hi, > > Probably this was already discussed, but I just want to send a reminder. > > The download button at the top should point to 1.3. Yes, but Adrian is on Holidays in India and I can't change it (at least I have not found out how). I think I wil pester the hotline of Cmsbox (even though we are technically not a customer ;-) Marcus -- Marcus Denker -- http://marcusdenker.de

Sept. 23, 2011

[Pharo-project] Pharo Sprint November 2011 - Noviembre 2011 @ Smalltalks 2011

by Guillermo Polito

Hi! I'm gathering the attendants the Pharo Sprint the day before the Smalltalks2011 in Universidad Nacional de Quilmes, so we can guess the space and other requirements needed. If you are attending, please fill the form below :). Estoy juntando a la gente que quiera participar del Pharo Sprint el dÃa previo a la Smalltalks, en la Universidad Nacional de Quilmes. Si queres participar, completÃ¡ el formulario de abajo. Gracias, Thanks! Guille Si tienes problemas para visualizar o enviar este formulario, puedes rellenarlo online: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dHlKdUdvYnF3c3… Pharo Sprint November 2011 - Noviembre 2011 I will attend to the Pharo Sprint on november 2 of 2011, from 2pm to 8pm, at Universidad Nacional de Quilmes, the day previous to the conference. AsistirÃ© al Pharo Sprint del miÃ©rcoles 2 de noviembre de 2011, desde las 14:00 a las 20:00, en la UNQui, dÃa previo a la conferencia. First and Last Name - Nombre y Apellido * Email * Con la tecnologÃa de Google Docs <http://docs.google.com> Informar sobre abusos<https://spreadsheets.google.com/spreadsheet/reportabuse?formkey=dHlKdUdvYnF…>- Condiciones del servicio <http://www.google.com/accounts/TOS> - Otros tÃ©rminos<http://www.google.com/google-d-s/terms.html>

Sept. 23, 2011

[Pharo-project] Pharo web page download button

by Noury Bouraqadi

Hi, Probably this was already discussed, but I just want to send a reminder. The download button at the top should point to 1.3. Thanks for all Pharo contributors, Noury -- http://twitter.com/#!/NouryBouraqadi

Sept. 23, 2011

Re: [Pharo-project] Class creation notification

by StÃ©phane Ducasse

you should have also the browser and the recentMessageList look for event: Stef On Sep 23, 2011, at 7:52 PM, Mariano Martinez Peck wrote: > Hi guys. I was checking who needs to be notified when a class is created. If I follow correctly senders of #notify:ofSystemChangesOfItem:change:using: and friends, I don't really find too many listeners. I found TestRunner >> initialize and MCPackageManager > > > -- > Mariano > http://marianopeck.wordpress.com >

Sept. 23, 2011

Re: [Pharo-project] Pharo for iOS

by Alexandre Bergel

Right. You need to provide your Id. Ask Bert directly. Alexandre On 23 Sep 2011, at 16:00, Marcus Denker wrote: > > On Sep 23, 2011, at 8:56 PM, Alexandre Bergel wrote: > >> Actually, you have to install DrGeo. >> http://dl.dropbox.com/u/9643745/DrGeo/DrGeoTestBF.html >> >> You can then use whatever image you wish instead, by just dragging and dropping it from your desktop to iTunes. >> > > *but* isn't that binary compiled to run only on certain ipads? Like yours and a handful of others? > > Marcus > > -- > Marcus Denker -- http://marcusdenker.de > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 23, 2011

Re: [Pharo-project] jenkis is down

by Marcus Denker

Yes, known problem and reported since yesterday... On Sep 23, 2011, at 7:31 PM, Mariano Martinez Peck wrote: > > > -- > Mariano > http://marianopeck.wordpress.com > -- Marcus Denker -- http://marcusdenker.de

Sept. 23, 2011

Re: [Pharo-project] Pharo for iOS

by Marcus Denker

On Sep 23, 2011, at 8:56 PM, Alexandre Bergel wrote: > Actually, you have to install DrGeo. > http://dl.dropbox.com/u/9643745/DrGeo/DrGeoTestBF.html > > You can then use whatever image you wish instead, by just dragging and dropping it from your desktop to iTunes. > *but* isn't that binary compiled to run only on certain ipads? Like yours and a handful of others? Marcus -- Marcus Denker -- http://marcusdenker.de

Sept. 23, 2011

Re: [Pharo-project] Pharo for iOS

by Alexandre Bergel

Actually, you have to install DrGeo. http://dl.dropbox.com/u/9643745/DrGeo/DrGeoTestBF.html You can then use whatever image you wish instead, by just dragging and dropping it from your desktop to iTunes. Alexandre On 23 Sep 2011, at 13:41, Pat Maddox wrote: > sweet! where can I find instructions on how to do this too? > > > On Sep 22, 2011, at 4:37 AM, Alexandre Bergel wrote: > >> I have Pharo running on my ipad. >> I just followed instruction of Bert and it works like a charm. This is not accesible via itune however, but, it is perfectly okay to have pharo applications on it. John has a couple of them >> >> Alexandre >> >> >> On 22 Sep 2011, at 06:46, Dennis Schetinin wrote: >> >>> What is the state of the art and nearest perspectives of using Pharo/Squea (or maybe some other Smalltalk implementation) for iOS development? And does Apple officially allow to Smalltalk-based applications? >>> >>> -- >>> Dennis Schetinin >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 23, 2011

Re: [Pharo-project] Class creation notification

by Alexandre Bergel

> grrr shorcuts.. then I found AutomaticMethodCategorizerApplier which I don't care. +1 > And I don't care if I need to close and open again the TestRunner. -1 Alexandre > > So....what I mean is that class creation notification increases Fuel classes materialization like 50%. Do you think this is un-important enough to provide a way to NOT notify? I mean, should I provide a way to avoid that and avoid the 50% ? or it will be totally unsafe? > > Thanks! > > > > > On Fri, Sep 23, 2011 at 7:52 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Hi guys. I was checking who needs to be notified when a class is created. If I follow correctly senders of #notify:ofSystemChangesOfItem:change:using: and friends, I don't really find too many listeners. I found TestRunner >> initialize and MCPackageManager > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 23, 2011

[Pharo-project] new Cog VMs available [please read]

by Eliot Miranda

Hi All, yesterday's new VMs bore fruit and I found and fixed a bug that could cause fatal VM crashes. Alas it was not the one I was looking for, simply closely related. So I've uploaded new VMs to http://www.mirandabanda.org/files/Cog/VM/VM.r2494/README.2494 and would ask you, especially if you used yesterday's VM, to upgrade to today's VM and hopefully I can nail the one I was after in the first place. thanks for the great response! Eliot P.S. Here's the readme, and a reiteration of what I need from you CogVM source as per VMMaker.oscog-eem.126. Fix cPICEndSize mis-computation caused by using rounded-up closedPICSize. Compute cPICEndSize and /then/ round-up closedPICSize. These VMs are not much changed from the 2487 VMs, BUT the 2487 VMs introduced a bug while providing faster doesNotUnderstand: processing. These 2494 VMs contain code to help identify that bug. If you're already using a 2487 VM or newer /please/ upgrade to these 2494 VMs asap. I want to see C stack backtraces from these VMs whenever they crash. Typically the VMs produce a crash.dmp file somewhere in the file system (may be / on Mac OS, may be in the directory containing the VM or the current directory on other OSs, but it will be called crash.dmp, and on Mac OS info will be printed to the console or to a crash report window). The C backtrace part of things looks like this on windows: Stack backtrace: [004193EA] ??? + 4297706 in CogCode [00442337] ??? + 4465463 in CogCode [00442685] ??? + 4466309 in CogCode [00583018] ??? + 5779480 in CogCode [0040124B] ??? + 4198987 in CogCode [00401298] ??? + 4199064 in CogCode [7C816FE7] RegisterWaitForInputIdle + 73 in kernel32.dll [7C913BA7] RtlDosApplyFileIsolationRedirection_Ustr + 1824 in ntdll.dll this on Mac C stack backtrace: 0 nsvm 0x00038689 reportStackState + 105 1 nsvm 0x0003893e sigsegv + 110 2 libsystem_c.dylib 0x9b2e259b _sigtramp + 43 3 ??? 0xffffffff 0x0 + 4294967295 4 nsvm 0x0008b2a5 sufficientSpaceAfterGC + 69 5 nsvm 0x0008d11d primitiveNewWithArg + 221 6 ??? 0x068b9899 0x0 + 109811865 7 nsvm 0x00098d10 initStackPagesAndInterpret + 512 8 nsvm 0x0002c530 EventLoopEventHandler + 16 Etc. So please feel free to email me the crash.dmp's and/or the C backtraces of any crashes you have with 2494 VMs. Hopefully I'll track down this regression quickly. For the curious, what's the bug? I don't know yet. The symptom is that very rarely the inline cache linking machinery for MNU PICs relinks the call of an MNU PIC to the address 0x00000013, which causes a crash when the call is next executed, long after the bug bit. These VMs contain code that will raise an error when the relinking attempt is made, which should reveal the bug. On Thu, Sep 22, 2011 at 10:37 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > ...in http://www.mirandabanda.org/files/Cog/VM/VM.r2493/. These VMs are > not much changed from the 2487 VMs, BUT the 2487 VMs introduced a bug while > providing faster doesNotUnderstand: processing. These 2493 VMs contain code > to help identify that bug. If you're already using a 2487 VM or newer > /please/ upgrade to these 2493 VMs asap. I want to see C stack backtraces > from these VMs whenever they crash. Typically the VMs produce a crash.dmp > file somewhere in the file system (may be / on Mac OS, may be in the > directory containing the VM or the current directory on other OSs, but it > will be called crash.dmp, and on Mac OS info will be printed to the console > or to a crash report window). The C backtrace part of things looks like > > this on windows: > Stack backtrace: > [004193EA] ??? + 4297706 in CogCode > [00442337] ??? + 4465463 in CogCode > [00442685] ??? + 4466309 in CogCode > [00583018] ??? + 5779480 in CogCode > [0040124B] ??? + 4198987 in CogCode > [00401298] ??? + 4199064 in CogCode > [7C816FE7] RegisterWaitForInputIdle + 73 in kernel32.dll > [7C913BA7] RtlDosApplyFileIsolationRedirection_Ustr + 1824 in ntdll.dll > > this on Mac > C stack backtrace: > 0 nsvm 0x00038689 reportStackState + 105 > 1 nsvm 0x0003893e sigsegv + 110 > 2 libsystem_c.dylib 0x9b2e259b _sigtramp + 43 > 3 ??? 0xffffffff 0x0 + 4294967295 > 4 nsvm 0x0008b2a5 sufficientSpaceAfterGC + > 69 > 5 nsvm 0x0008d11d primitiveNewWithArg + > 221 > 6 ??? 0x068b9899 0x0 + 109811865 > 7 nsvm 0x00098d10 > initStackPagesAndInterpret + 512 > 8 nsvm 0x0002c530 EventLoopEventHandler + > 16 > > Etc. So please feel free to email me the crash.dmp's and/or the C > backtraces of any crashes you have with 2493 VMs. Hopefully I'll track down > this regression quickly. > > For the curious, what's the bug? I don't know yet. The symptom is that > very rarely the inline cache linking machinery for MNU PICs relinks the call > of an MNU PIC to the address 0x00000013, which causes a crash when the call > is next executed, long after the bug bit. These VMs contain code that will > raise an error when the relinking attempt is made, which should reveal the > bug. > > Here's the 2493 readme: > > CogVM binaries as per VMMaker.oscog-eem.125/r2493. Add callsite link/relocate > checks to catch the call 0x00000013 MNU callsite relinking bug. > Reduce the size of the simStack to something proportional to LargeContextSize. > > In the Newspeak VM, don't cd to the image's directory on win32. Fix off-by-one > error in Win32OSProcessPlugin>primitiveGetCurrentWorkingDirectory so it doesn't > include an erroneous trailing null. > > Fix the 1Gb allocation bug. > > -- > best, > Eliot > > -- best, Eliot

Sept. 23, 2011