- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pointer Detective

by Mariano Martinez Peck

Hi Ben, Very nice tool! Thank you very much for it. Question....do you think it is possible to add a feature that it automatically builds the whole graph starting at target object until the GC root that is holding it? In Pharo, the GC root is the special object array (see #newSpecialObjectsArray). So the code should basically do a loop for #pointersTo and check if one of those pointers is directly one of the array. Or something like that like. Probably it will crash the VM hahaha. But it would be nice to track from a certain object up to the GC root and see all that path in graph :) On Tue, Sep 2, 2014 at 4:41 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Oh yes, this is essential part of âworking with objectsâ. No? > > > On 02 Sep 2014, at 21:37, Max Leske <maxleske(a)gmail.com> wrote: > > > You are my hero! I was just complaining about that to Doru at ESUG. This > sort of tool should be part of the standard tool set so please keep on > improving it and weâll try to convince someone to integrate it :) > > > > Max > > > > On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: > > > >> greetings all, > >> > >> I had an itch to scratch... I find it difficult using the tree list of > the standard Pointer Explorer to track down why objects aren't garbage > collected. I always fear I'm not going to notice getting caught in a > reference loop. So I created a tool presenting an alternative view as a > directed graph. The graph incrementally builds out from the target object > as you explore it. Nodes are colourised to help manage complexity. > >> > >> The attached snapshot is produced from evaluating the following > Workspace script... > >> testObject := 'END5'. > >> ref1 := { testObject. nil }. > >> ref2 := { ref1 }. > >> ref3 := PDTestResource new heldObject: ref2. > >> ref1 at: 2 put: ref3. "note the reference loop this creates" > >> PointerDetective openOn: testObject. > >> > >> Now I expect I'm duplicating something done before, but I couldn't find > anything quickly and it was an opportunity for some goal direct learning of > Morphic. Thanks to Roassal an option for a spring-force layout is provided. > That code was copied rather than create a dependency, and might need to be > rationalized later. > >> The code is a bit rough from hacking around learning how to make things > work, but its functional, so its time to get it out in the open. > >> > >> For more information please refer to the repository home page... > >> http://smalltalkhub.com/#!/~BenComan/PointerDetective > >> > >> cheers -ben > >> <PointerDetectiveExample1.png> > > > > > > > -- Mariano http://marianopeck.wordpress.com

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Yuriy Tymchuk

Oh yes, this is essential part of âworking with objectsâ. No? On 02 Sep 2014, at 21:37, Max Leske <maxleske(a)gmail.com> wrote: > You are my hero! I was just complaining about that to Doru at ESUG. This sort of tool should be part of the standard tool set so please keep on improving it and weâll try to convince someone to integrate it :) > > Max > > On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: > >> greetings all, >> >> I had an itch to scratch... I find it difficult using the tree list of the standard Pointer Explorer to track down why objects aren't garbage collected. I always fear I'm not going to notice getting caught in a reference loop. So I created a tool presenting an alternative view as a directed graph. The graph incrementally builds out from the target object as you explore it. Nodes are colourised to help manage complexity. >> >> The attached snapshot is produced from evaluating the following Workspace script... >> testObject := 'END5'. >> ref1 := { testObject. nil }. >> ref2 := { ref1 }. >> ref3 := PDTestResource new heldObject: ref2. >> ref1 at: 2 put: ref3. "note the reference loop this creates" >> PointerDetective openOn: testObject. >> >> Now I expect I'm duplicating something done before, but I couldn't find anything quickly and it was an opportunity for some goal direct learning of Morphic. Thanks to Roassal an option for a spring-force layout is provided. That code was copied rather than create a dependency, and might need to be rationalized later. >> The code is a bit rough from hacking around learning how to make things work, but its functional, so its time to get it out in the open. >> >> For more information please refer to the repository home page... >> http://smalltalkhub.com/#!/~BenComan/PointerDetective >> >> cheers -ben >> <PointerDetectiveExample1.png> > >

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Max Leske

You are my hero! I was just complaining about that to Doru at ESUG. This sort of tool should be part of the standard tool set so please keep on improving it and weâll try to convince someone to integrate it :) Max On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: > greetings all, > > I had an itch to scratch... I find it difficult using the tree list of the standard Pointer Explorer to track down why objects aren't garbage collected. I always fear I'm not going to notice getting caught in a reference loop. So I created a tool presenting an alternative view as a directed graph. The graph incrementally builds out from the target object as you explore it. Nodes are colourised to help manage complexity. > > The attached snapshot is produced from evaluating the following Workspace script... > testObject := 'END5'. > ref1 := { testObject. nil }. > ref2 := { ref1 }. > ref3 := PDTestResource new heldObject: ref2. > ref1 at: 2 put: ref3. "note the reference loop this creates" > PointerDetective openOn: testObject. > > Now I expect I'm duplicating something done before, but I couldn't find anything quickly and it was an opportunity for some goal direct learning of Morphic. Thanks to Roassal an option for a spring-force layout is provided. That code was copied rather than create a dependency, and might need to be rationalized later. > The code is a bit rough from hacking around learning how to make things work, but its functional, so its time to get it out in the open. > > For more information please refer to the repository home page... > http://smalltalkhub.com/#!/~BenComan/PointerDetective > > cheers -ben > <PointerDetectiveExample1.png>

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Thierry Goubier

Thanks Ben, I think this will be very helpfull :) Could you add a ConfigurationOfPointerDetective in the meta repo to enable an easy access? Thierry Le 02/09/2014 19:40, Ben Coman a Ã©crit : > greetings all, > > I had an itch to scratch... I find it difficult using the tree list > of the standard Pointer Explorer to track down why objects aren't > garbage collected. I always fear I'm not going to notice getting > caught in a reference loop. So I created a tool presenting an > alternative view as a directed graph. The graph incrementally builds > out from the target object as you explore it. Nodes are colourised to > help manage complexity. > > The attached snapshot is produced from evaluating the following > Workspace script... > testObject := 'END5'. > ref1 := { testObject. nil }. > ref2 := { ref1 }. > ref3 := PDTestResource new heldObject: ref2. > ref1 at: 2 put: ref3. "note the reference loop this creates" > PointerDetective openOn: testObject. > > Now I expect I'm duplicating something done before, but I couldn't > find anything quickly and it was an opportunity for some goal direct > learning of Morphic. Thanks to Roassal an option for a spring-force > layout is provided. That code was copied rather than create a > dependency, and might need to be rationalized later. > The code is a bit rough from hacking around learning how to make > things work, but its functional, so its time to get it out in the open. > > For more information please refer to the repository home page... > http://smalltalkhub.com/#!/~BenComan/PointerDetective > > cheers -ben

Sept. 2, 2014

Any changes with fonts?

by Yuriy Tymchuk

Hi, when I cannot see system fonts anymore after selecting Free Type font checkbox in settings. Are there any changes to fonts? Of something broke down? Uko

Sept. 2, 2014

[ANN] Pointer Detective

by Ben Coman

greetings all, I had an itch to scratch... I find it difficult using the tree list of the standard Pointer Explorer to track down why objects aren't garbage collected. I always fear I'm not going to notice getting caught in a reference loop. So I created a tool presenting an alternative view as a directed graph. The graph incrementally builds out from the target object as you explore it. Nodes are colourised to help manage complexity. The attached snapshot is produced from evaluating the following Workspace script... testObject := 'END5'. ref1 := { testObject. nil }. ref2 := { ref1 }. ref3 := PDTestResource new heldObject: ref2. ref1 at: 2 put: ref3. "note the reference loop this creates" PointerDetective openOn: testObject. Now I expect I'm duplicating something done before, but I couldn't find anything quickly and it was an opportunity for some goal direct learning of Morphic. Thanks to Roassal an option for a spring-force layout is provided. That code was copied rather than create a dependency, and might need to be rationalized later. The code is a bit rough from hacking around learning how to make things work, but its functional, so its time to get it out in the open. For more information please refer to the repository home page... http://smalltalkhub.com/#!/~BenComan/PointerDetective cheers -ben

Sept. 2, 2014

Re: [Pharo-dev] Rewrite rules doc?

by Sean P. DeNigris

Uko2 wrote > Is there any doc about rewrite rules... A few mailing list discussions which stand out: - http://forum.world.st/Adding-a-statement-when-rewriting-td4668879.html - http://forum.world.st/RB-API-td3781019.html - http://forum.world.st/Classes-referenced-in-code-string-td4244214.html - http://forum.world.st/Adding-a-statement-programmatically-tp4454447p4459879… Also, I found http://www.refactory.com/tools/refactoring-browser/rewrite-tool to be quite helpful re the basics... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Rewrite-rules-doc-tp4775759p4775829.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2014

Re: [Pharo-dev] When all you have is Spec, everything looks like a nail?

by Sean P. DeNigris

philippeback wrote > ButtonModel new > label: 'Click me'; > whenActionPerformedDo: [Transcript show: 'Clicked!' ]; > openWithSpec. Just what I hoped for this thread - that we would all learn some cool things! And, Steph answered my concern right away with "So we will see and learn. But I can tell you that nothing is carved in stone". Perfect. ----- Cheers, Sean -- View this message in context: http://forum.world.st/When-all-you-have-is-Spec-everything-looks-like-a-nai… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2014

Re: [Pharo-dev] Rewrite rules doc?

by stepharo

look in the notes folder inside the ParseTreeRewriter chapter on github. Normally I collected all the information I could find and this is why we will continue to write and finish this chapter with mark. st On 2/9/14 14:18, Yuriy Tymchuk wrote: > Hi guys. Is there any doc about rewrite rules besides > https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/lastSucces… ? > > Uko > >

Sept. 2, 2014

Re: [Pharo-dev] NonInteractiveTranscript and Debugging issue in headless image

by Sven Van Caekenberghe

I see that you (your code / the code you load) explicitly wants to open a debugger, which cannot be done non-interactively as far as I know. That is the root problem I think. When running non-interactive you either let errors/warnings/notifications bubble up and they will be handled appropriately or you handle them yourself (like ignoring merge warnings, answering simple questions like author). On 02 Sep 2014, at 17:30, phil(a)highoctane.be wrote: > I've got this error when the debugger is triggered in a headless image. > > So, #MNU. > > I had a look at the NonInteractiveTranscript and it has this method missing indeed in 3.0. > > I've added a basic one but we could benefit from enhanced debugging abilities on that front. > > As I am running on a server without any graphics abilities, it would be welcome to have this fixed. > > I added this to the startup script to patch the thing: > > Author fullName: 'PhilippeBack'. "Avoid yet another question..." > > NonInteractiveUIManager compile: 'openDebuggerOn: process context: context label: title contents: contentsStringOrNil fullView: bool > > ^ self nonInteractiveWarning: ''Opening Debugger''' classified: #'ui-requests'. > > So far so good, but it turned to: > > An attempt to use interactive tools detected, while in non-interactive mode > Opening Debugger > NonInteractiveUIManager>>nonInteractiveWarning: > NonInteractiveUIManager>>openDebuggerOn:context:label:contents:fullView: > SpecDebugger class>>openOn:context:label:contents:fullView: > Process>>debug:title:full: > GRPharoPlatform>>openDebuggerOn: in Block: [ process debug: anError signalerContext title: an...etc... > > And the vm stopped again. > > Looks like: > > NonInteractiveUIManager>>nonInteractiveWarning: aWarnMessage > ^ ErrorNonInteractive signal: aWarnMessage > > isn't too friendly. > > How would one get debugging info shown and just proceed or close the debugger? > > Closing the image is really hard to swallow here. > > Ideas? > > Phil > > > > > > > <NIT.png>

Sept. 2, 2014