May 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by Esteban A. Maringolo

2017-05-10 13:38 GMT-03:00 ClÃ©ment Bera <bera.clement(a)gmail.com>: > On Wed, May 10, 2017 at 5:28 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> If it is a plug-in, why does it need VM recompilation? > > Internal plugins require VM recompilation. Only external plugins do not. It was more of a semantic question, I'd expect a plug-in to be that, pluggable, as you say external plugins are. Or what is the "pluggability" of such plugins? Disclaimer: I don't know about the VM internals (*), and this is not a complain of any sort. I just wonder it is called that way. Regards! Esteban A. Maringolo (*) I did compile a Squeak VM a decade ago (added two primitives) but nothing more than that.

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by Sophie Kaleba

Thanks for your help! @Nicolas, I'll do it that way 2017-05-10 17:15 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > Hi Sophie, > you could try and modify the plugins.int or plugins.ext files for various > pharo distributions and do a pull request on github opensmalltalk-vm. > Then let Esteban accept the request or not before the release of Pharo... > (if the build are green, there's no reason to not accept it). > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > >> OK, I see. >> >> >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hi Max, >> >> She has already done that. The point is to add the plugins in the default >> Pharo VM, so everyone can use the VM profiler. We would like to have the VM >> profiler loadable through the Pharo catalog, but many people won't be able >> to use it if the default Pharo VM does not support it... >> >> The plugin is lightweight, so I don't see why we can't have it. >> >> Best, >> >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: >> >>> Hi Sophie, >>> >>> You will have to compile your own VM for the moment. It's fairly easy >>> but you might run into problems when including the extra plugin. To build >>> the VM, follow the instructions on https://github.com/OpenSmal >>> ltalk/opensmalltalk-vm and read the README and HOWTO files. Simple >>> build example: >>> >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d >>> >>> will build a debug VM. You'll have to modify one of the "plugins.*" >>> files to include the plugin. >>> >>> HTH, >>> Max >>> >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: >>> >>> Hi Esteban, Hi all, >>> >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will >>> post a more detailed presentation about that in the mailing list later >>> today). >>> >>> While trying to use the profiler with the Pharo VM, I get the following >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >>> >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included >>> by default in the Pharo VM (it works with a Squeak VM). I haven't tried on >>> a mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >>> >>> For the moment, I am using the latest Squeak VM with my Pharo image but >>> it is not quite convenient. Would it be possible to include the 2 plugins >>> to the Pharo VM ? >>> >>> If I can be of any help, just tell me >>> Thanks! >>> >>> Sophie >>> >>> >>> >>> >>> >>> >>> <PrimitiveFailed.jpg> >>> >>> >>> >> >> >

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by ClÃ©ment Bera

On Wed, May 10, 2017 at 5:28 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > If it is a plug-in, why does it need VM recompilation? > Internal plugins require VM recompilation. Only external plugins do not. > > Esteban A. Maringolo > > > > > > > 2017-05-10 12:15 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com>: > > Hi Sophie, > > you could try and modify the plugins.int or plugins.ext files for > various > > pharo distributions and do a pull request on github opensmalltalk-vm. > > Then let Esteban accept the request or not before the release of Pharo... > > (if the build are green, there's no reason to not accept it). > > > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > >> > >> OK, I see. > >> > >> > >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > >> > >> Hi Max, > >> > >> She has already done that. The point is to add the plugins in the > default > >> Pharo VM, so everyone can use the VM profiler. We would like to have > the VM > >> profiler loadable through the Pharo catalog, but many people won't be > able > >> to use it if the default Pharo VM does not support it... > >> > >> The plugin is lightweight, so I don't see why we can't have it. > >> > >> Best, > >> > >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: > >>> > >>> Hi Sophie, > >>> > >>> You will have to compile your own VM for the moment. It's fairly easy > but > >>> you might run into problems when including the extra plugin. To build > the > >>> VM, follow the instructions on > >>> https://github.com/OpenSmalltalk/opensmalltalk-vm and read the README > and > >>> HOWTO files. Simple build example: > >>> > >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d > >>> > >>> will build a debug VM. You'll have to modify one of the "plugins.*" > files > >>> to include the plugin. > >>> > >>> HTH, > >>> Max > >>> > >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> > wrote: > >>> > >>> Hi Esteban, Hi all, > >>> > >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I > will > >>> post a more detailed presentation about that in the mailing list later > >>> today). > >>> > >>> While trying to use the profiler with the Pharo VM, I get the following > >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in > >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). > >>> > >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included > by > >>> default in the Pharo VM (it works with a Squeak VM). I haven't tried > on a > >>> mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. > >>> > >>> For the moment, I am using the latest Squeak VM with my Pharo image but > >>> it is not quite convenient. Would it be possible to include the 2 > plugins to > >>> the Pharo VM ? > >>> > >>> If I can be of any help, just tell me > >>> Thanks! > >>> > >>> Sophie > >>> > >>> > >>> > >>> > >>> > >>> > >>> <PrimitiveFailed.jpg> > >>> > >>> > >> > >> > > > >

May 10, 2017

Re: [Pharo-dev] GSoC 2017 Introduction

by Ben Coman

Welcome Myro, Good to see you getting involved early in the process. I understand you bumped into Pharo at your university, but there seems no great Pharo presence there. I'd be interested to hear a bit more about how you discovered Pharo. cheers -ben On Wed, May 10, 2017 at 4:58 AM, Myroslava Romaniuk <romaniuk(a)ucu.edu.ua> wrote: > Hello everyone > > I have been accepted as a GSoC student and my project is Advancing in Pharo > Quality Support. Here's the link to my proposal, if you have any suggestions > feel free to comment or send me an email, I would really appreciate some > feedback. Here are also links to my github and linkedin. > > In short, my project consists of several subprojects: > > updating rules (improving hints, moving the rules to corresponding packages) > advanced rule toggle (a functionality to enable/disable rules from Pharo > settings, a shortcut to ban a rule globally) > smart error handling (display errors that occured during critique > computation along the actual critiques) > match-rewrite tool (combines features of matchtool and rewritetool, improves > the process of inspecting, creating, editing and removing rules) > pre-commit quality feedback (an extension to either monticello or iceberg > that will show modified parts of a project and critiques related to them --- > if I have time) > making rules more maintainable while reporting encountered bugs > > Thanks very much for this amazing opportunity to be working with all of you, > and for the help you're providing us, GSoC students, with - on Discord and > in the mailing list. > > Looking forward to the amazing summer with the Pharo community! > > -- Myroslava

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by Esteban A. Maringolo

If it is a plug-in, why does it need VM recompilation? Esteban A. Maringolo 2017-05-10 12:15 GMT-03:00 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Hi Sophie, > you could try and modify the plugins.int or plugins.ext files for various > pharo distributions and do a pull request on github opensmalltalk-vm. > Then let Esteban accept the request or not before the release of Pharo... > (if the build are green, there's no reason to not accept it). > > 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: >> >> OK, I see. >> >> >> On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hi Max, >> >> She has already done that. The point is to add the plugins in the default >> Pharo VM, so everyone can use the VM profiler. We would like to have the VM >> profiler loadable through the Pharo catalog, but many people won't be able >> to use it if the default Pharo VM does not support it... >> >> The plugin is lightweight, so I don't see why we can't have it. >> >> Best, >> >> On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> Hi Sophie, >>> >>> You will have to compile your own VM for the moment. It's fairly easy but >>> you might run into problems when including the extra plugin. To build the >>> VM, follow the instructions on >>> https://github.com/OpenSmalltalk/opensmalltalk-vm and read the README and >>> HOWTO files. Simple build example: >>> >>> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d >>> >>> will build a debug VM. You'll have to modify one of the "plugins.*" files >>> to include the plugin. >>> >>> HTH, >>> Max >>> >>> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: >>> >>> Hi Esteban, Hi all, >>> >>> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will >>> post a more detailed presentation about that in the mailing list later >>> today). >>> >>> While trying to use the profiler with the Pharo VM, I get the following >>> error : "PrimitiveFailed : primitive #primitiveExecutableModules in >>> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >>> >>> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included by >>> default in the Pharo VM (it works with a Squeak VM). I haven't tried on a >>> mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >>> >>> For the moment, I am using the latest Squeak VM with my Pharo image but >>> it is not quite convenient. Would it be possible to include the 2 plugins to >>> the Pharo VM ? >>> >>> If I can be of any help, just tell me >>> Thanks! >>> >>> Sophie >>> >>> >>> >>> >>> >>> >>> <PrimitiveFailed.jpg> >>> >>> >> >> >

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by Nicolas Cellier

Hi Sophie, you could try and modify the plugins.int or plugins.ext files for various pharo distributions and do a pull request on github opensmalltalk-vm. Then let Esteban accept the request or not before the release of Pharo... (if the build are green, there's no reason to not accept it). 2017-05-10 15:39 GMT+02:00 Max Leske <maxleske(a)gmail.com>: > OK, I see. > > > On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Hi Max, > > She has already done that. The point is to add the plugins in the default > Pharo VM, so everyone can use the VM profiler. We would like to have the VM > profiler loadable through the Pharo catalog, but many people won't be able > to use it if the default Pharo VM does not support it... > > The plugin is lightweight, so I don't see why we can't have it. > > Best, > > On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> Hi Sophie, >> >> You will have to compile your own VM for the moment. It's fairly easy but >> you might run into problems when including the extra plugin. To build the >> VM, follow the instructions on https://github.com/OpenSmal >> ltalk/opensmalltalk-vm and read the README and HOWTO files. Simple build >> example: >> >> cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d >> >> will build a debug VM. You'll have to modify one of the "plugins.*" files >> to include the plugin. >> >> HTH, >> Max >> >> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: >> >> Hi Esteban, Hi all, >> >> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will >> post a more detailed presentation about that in the mailing list later >> today). >> >> While trying to use the profiler with the Pharo VM, I get the following >> error : "PrimitiveFailed : primitive #primitiveExecutableModules in >> VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >> >> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included by >> default in the Pharo VM (it works with a Squeak VM). I haven't tried on a >> mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >> >> For the moment, I am using the latest Squeak VM with my Pharo image but >> it is not quite convenient. Would it be possible to include the 2 plugins >> to the Pharo VM ? >> >> If I can be of any help, just tell me >> Thanks! >> >> Sophie >> >> >> >> >> >> >> <PrimitiveFailed.jpg> >> >> >> > >

May 10, 2017

Re: [Pharo-dev] Adding class side inst.var to a class using Trait results in nil message sent

by Martin Dias

No problem. Just created case 20042 with this. On Wed, May 10, 2017 at 4:03 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Tx martin. > > On Wed, May 10, 2017 at 5:24 AM, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Ok... I reproduced it. It happens when the class uses a trait (via >> Metaclass>>uses:instanceVariableNames:) but no problem when no trait is >> used. I'll see what to do. >> >> Martin >> >> On Tue, May 9, 2017 at 4:22 PM, Stephane Ducasse <stepharo.self(a)gmail.com >> > wrote: >> >>> Aliaksei >>> thanks for the report. Now if you do not say in the title that this >>> looks like an Epicea problem >>> then Martin may not see it. >>> Can you open a bug entry? >>> Stef >>> >>> On Mon, May 8, 2017 at 10:57 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> >>> wrote: >>> >>>> Hi, >>>> >>>> Screenshot tells everything :) >>>> I was trying to add "asdasd" inst var >>>> >>>> [image: Inline images 1] >>>> >>>> Cheers, >>>> Alex >>>> >>> >>> >> >

May 10, 2017

GSOC introduction

by Sophie Kaleba

Hi everyone, I have been accepted as a Google Summer of Code student to work on improving the VMProfiler. The project can be divided in 2 parts : - first, the idea is to port the VMProfiler to Pharo (as it only works on Squeak for now), to eventually have a version working both in Squeak and Pharo. - once the porting is done, the aim is to enhance the profiler itself ; when profiling code generated by the JIT, the profiler should be able to show where the time is spent in specific methods, rather than just telling in which methods the time is spent. I may be able to share with you a first version of a Squeak/Pharo profiler soon. Then feel free to try it out and give me your feedback ! Of course, any suggestion/question/feedback on the project is welcome Thanks for the opportunity ! Sophie

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by Max Leske

OK, I see. > On 10 May 2017, at 15:11, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Hi Max, > > She has already done that. The point is to add the plugins in the default Pharo VM, so everyone can use the VM profiler. We would like to have the VM profiler loadable through the Pharo catalog, but many people won't be able to use it if the default Pharo VM does not support it... > > The plugin is lightweight, so I don't see why we can't have it. > > Best, > > On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com <mailto:maxleske@gmail.com>> wrote: > Hi Sophie, > > You will have to compile your own VM for the moment. It's fairly easy but you might run into problems when including the extra plugin. To build the VM, follow the instructions on https://github.com/OpenSmalltalk/opensmalltalk-vm <https://github.com/OpenSmalltalk/opensmalltalk-vm> and read the README and HOWTO files. Simple build example: > > cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d > > will build a debug VM. You'll have to modify one of the "plugins.*" files to include the plugin. > > HTH, > Max > >> On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com <mailto:sophie.kaleba@gmail.com>> wrote: >> >> Hi Esteban, Hi all, >> >> I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will post a more detailed presentation about that in the mailing list later today). >> >> While trying to use the profiler with the Pharo VM, I get the following error : "PrimitiveFailed : primitive #primitiveExecutableModules in VMProfilerLinuxSymbolsManager failed". (see stack trace attached). >> >> This plugin (VMProfileLinuxSupportPlugin) does not seem to be included by default in the Pharo VM (it works with a Squeak VM). I haven't tried on a mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. >> >> For the moment, I am using the latest Squeak VM with my Pharo image but it is not quite convenient. Would it be possible to include the 2 plugins to the Pharo VM ? >> >> If I can be of any help, just tell me >> Thanks! >> >> Sophie >> >> >> >> >> >> >> <PrimitiveFailed.jpg> > >

May 10, 2017

Re: [Pharo-dev] Missing plugins to make the vmProfiler work on Pharo

by ClÃ©ment Bera

Hi Max, She has already done that. The point is to add the plugins in the default Pharo VM, so everyone can use the VM profiler. We would like to have the VM profiler loadable through the Pharo catalog, but many people won't be able to use it if the default Pharo VM does not support it... The plugin is lightweight, so I don't see why we can't have it. Best, On Wed, May 10, 2017 at 3:00 PM, Max Leske <maxleske(a)gmail.com> wrote: > Hi Sophie, > > You will have to compile your own VM for the moment. It's fairly easy but > you might run into problems when including the extra plugin. To build the > VM, follow the instructions on https://github.com/ > OpenSmalltalk/opensmalltalk-vm and read the README and HOWTO files. > Simple build example: > > cd ~/git/opensmalltalk-vm/build.macos32x86/pharo.cog.spur/ && ./mvm -d > > will build a debug VM. You'll have to modify one of the "plugins.*" files > to include the plugin. > > HTH, > Max > > On 10 May 2017, at 14:36, Sophie Kaleba <sophie.kaleba(a)gmail.com> wrote: > > Hi Esteban, Hi all, > > I am working on porting the Squeak VMProfiler to Pharo as a gsoc (I will > post a more detailed presentation about that in the mailing list later > today). > > While trying to use the profiler with the Pharo VM, I get the following > error : "PrimitiveFailed : primitive #primitiveExecutableModules in > VMProfilerLinuxSymbolsManager failed". (see stack trace attached). > > This plugin (VMProfileLinuxSupportPlugin) does not seem to be included by > default in the Pharo VM (it works with a Squeak VM). I haven't tried on a > mac, but I guess the plugin (VMProfileMacSupportPlugin) is missing too. > > For the moment, I am using the latest Squeak VM with my Pharo image but it > is not quite convenient. Would it be possible to include the 2 plugins to > the Pharo VM ? > > If I can be of any help, just tell me > Thanks! > > Sophie > > > > > > > <PrimitiveFailed.jpg> > > >

May 10, 2017