- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ANN] The Jejak Trace framework

by StÃ©phane Ducasse

> >> I announce the first availability of the Jejak trace framework at >> >> http://ss3.gemstone.com/ss/Jejak.html >> >> During the VALMADEO project (a PRIR/RÃ©gion Bretagne funded project directed >> by C. Dezan, <dezan(a)univ-brest.fr>), we needed a tool to study in detail how >> some algorithms (error correcting codes) could work without errors, but with >> degraded performance. Execution and compilation would report no errors, but >> the performance of the error correcting coding and decoding would be several >> dB below the target. The error correcting code was looping hundreds of times >> over each block of data, making step by step debugging unusable. Profiling, >> message tallies were too coarse to tell us anything. We needed a different >> tool. >> >> The answer was this trace tool : a framework for injecting probes into >> methods, and record their execution. It can record an execution to the >> smallest detail (all calls, all values, all assignments), that over a long >> sequence (hundreds or thousands of calls), and let one navigate freely >> through the recorded trace along with the traced source code. It is capable >> of tracing system, startup or display methods, without interruption or >> blocking the overall image, allowing for very fine non-intrusive system >> analysis. > > This means one could get branch coverage analysis, doesn't it? We could then build a branch analysis of tests.

July 19, 2012

Re: [Pharo-project] [ANN] The Jejak Trace framework

by StÃ©phane Ducasse

Excellent. Thanks for releasing this code. Stef > I announce the first availability of the Jejak trace framework at > > http://ss3.gemstone.com/ss/Jejak.html > > During the VALMADEO project (a PRIR/RÃ©gion Bretagne funded project directed by C. Dezan, <dezan(a)univ-brest.fr>), we needed a tool to study in detail how some algorithms (error correcting codes) could work without errors, but with degraded performance. Execution and compilation would report no errors, but the performance of the error correcting coding and decoding would be several dB below the target. The error correcting code was looping hundreds of times over each block of data, making step by step debugging unusable. Profiling, message tallies were too coarse to tell us anything. We needed a different tool. > > The answer was this trace tool : a framework for injecting probes into methods, and record their execution. It can record an execution to the smallest detail (all calls, all values, all assignments), that over a long sequence (hundreds or thousands of calls), and let one navigate freely through the recorded trace along with the traced source code. It is capable of tracing system, startup or display methods, without interruption or blocking the overall image, allowing for very fine non-intrusive system analysis. > > It has been used for debugging turbo codes implementations, algorithm understanding on turbo codes, and memory behaviour analysis for embedded systems design space exploration. > > It requires The Opal compiler and is integrated with OmniBrowser, and is tested in a Pharo 1.4 image. Instructions for loading are : > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOmniBrowser'; > load. > > (ConfigurationOfOmniBrowser > project version: #stable) load: #( 'Dev' 'Dev Tests'). > > Gofer new > url: 'http://smalltalkhub.com/mc/MarcusDenker/Opal/main'; > package:'ConfigurationOfOpalCompiler'; > load. > > (Smalltalk at: #ConfigurationOfOpalCompiler) load. > > Gofer new > repository: 'http://ss3.gemstone.com/ss/Jejak'; > load > > There is a lot left to be done (better event logging, out of image logging, performance issues), but, as it is, it can be used for tracing almost any code in the image, even ones which may lock-up the image when halted (beware : bugs in the tracer may still lock or crash the image). It is also a very pedagogic way of seeing a full execution through a set of methods. > > Thierry > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 > >

July 19, 2012

Re: [Pharo-project] type inference in Pharo

by StÃ©phane Ducasse

did you tried roelTyper or the RBTypeGuesser? RoelTyper may have to be adapted to closure but the algorithm is documented in the DSL paper. Stef On Jul 18, 2012, at 4:23 PM, Alexandre Bergel wrote: >> So running type inference over "1 + e" will say "e is a SmallInteger", >> rather than "e is a Number". >> >> It uses abstract interpretation, if that answers your question? > > Well... not really. The problem I have is the following: I would like to compare two techniques to get dependencies between classes. One using a type inferencer and another using a profiler we have done. The hypothesis I would like to verify is that statically you always know less than by profiling the execution. > > However, it is difficult for me to use your type inferencer if I do not exactly know what is your algorithm. In a scientific publication, I cannot just put the url of the blog as a description of the algorithm. > > Cheers, > Alexandre > > >>> >>> On Jul 17, 2012, at 12:08 PM, Guillermo Polito wrote: >>> >>>> It's in the same blog: >>>> >>>> http://concretetypeinference.blogspot.fr/2012/05/about-how-i-got-here.html >>>> >>>> Cheers, >>>> Guille >>>> >>>> On Tue, Jul 17, 2012 at 6:03 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Hi! >>>> >>>> There is some work being done on inferring type (http://concretetypeinference.blogspot.com) What is the theoretical background of this work? >>>> What is the algorithm used to infer the types? >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

July 19, 2012

Re: [Pharo-project] failing tests

by StÃ©phane Ducasse

Excellent news indeed! > Hear, hear. We have no platform dependent test failure for Pharo 2.0! > > http://code.google.com/p/pharo/wiki/TestsGuard > > Thank you all for the great work

July 19, 2012

Re: [Pharo-project] [update 2.0] #20228

by Camillo Bruni

Now just don't ask how to reproduce it, cause I randomly changed things :D On 2012-07-19, at 19:15, Sven Van Caekenberghe wrote: > That is SUPER, that means that the SSL plugin finallly works! > > Me happy now ;-) > > Thx, > > Sven > > On 19 Jul 2012, at 18:38, Pavel Krivanek wrote: > >> Tests Guard report: http://code.google.com/p/pharo/wiki/TestsGuard >> >> Linux job is green. >> >> -- Pavel >> >> On Thu, Jul 19, 2012 at 5:51 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> 20228 >>> ----- >>> >>> Issue 3360: TextConverter handling of binary streams is wrong >>> http://code.google.com/p/pharo/issues/detail?id=3360 >>> >>> Issue 6411: MNU: Nautilus class>>newOnClass:selector: >>> http://code.google.com/p/pharo/issues/detail?id=6411 >>> >>> Issue 6427: use exitFailure in Pharo Kernel >>> http://code.google.com/p/pharo/issues/detail?id=6427 >>> >>> Issue 6426: Undeclared in ScriptLoader >>> http://code.google.com/p/pharo/issues/detail?id=6426 >>> >>> >>> >>> -- >>> Marcus Denker -- http://marcusdenker.de >>> >>> >> > >

July 19, 2012

[Pharo-project] R: aggg!!!!

by Lorenzo Schiavina

+1 Lorenzo -----Messaggio originale----- Da: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] Per conto di Francois Stephany Inviato: giovedÃ¬ 19 luglio 2012 18.39 A: pharo-project(a)lists.gforge.inria.fr Oggetto: Re: [Pharo-project] aggg!!!! +1 Don't be sorry Esteban you do an amzaing job! On 19/07/12 06:32, Sean P. DeNigris wrote: > > EstebanLM wrote >> >> I'm deeply sorry :S > > Sh*t happens. Great work and good catch :) > > -- > View this message in context: http://forum.world.st/aggg-tp4640708p4640720.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 19, 2012

Re: [Pharo-project] [update 2.0] #20228

by Sven Van Caekenberghe

That is SUPER, that means that the SSL plugin finallly works! Me happy now ;-) Thx, Sven On 19 Jul 2012, at 18:38, Pavel Krivanek wrote: > Tests Guard report: http://code.google.com/p/pharo/wiki/TestsGuard > > Linux job is green. > > -- Pavel > > On Thu, Jul 19, 2012 at 5:51 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> 20228 >> ----- >> >> Issue 3360: TextConverter handling of binary streams is wrong >> http://code.google.com/p/pharo/issues/detail?id=3360 >> >> Issue 6411: MNU: Nautilus class>>newOnClass:selector: >> http://code.google.com/p/pharo/issues/detail?id=6411 >> >> Issue 6427: use exitFailure in Pharo Kernel >> http://code.google.com/p/pharo/issues/detail?id=6427 >> >> Issue 6426: Undeclared in ScriptLoader >> http://code.google.com/p/pharo/issues/detail?id=6426 >> >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> >

July 19, 2012

Re: [Pharo-project] [update 2.0] #20228

by Pavel Krivanek

Tests Guard report: http://code.google.com/p/pharo/wiki/TestsGuard Linux job is green. -- Pavel On Thu, Jul 19, 2012 at 5:51 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 20228 > ----- > > Issue 3360: TextConverter handling of binary streams is wrong > http://code.google.com/p/pharo/issues/detail?id=3360 > > Issue 6411: MNU: Nautilus class>>newOnClass:selector: > http://code.google.com/p/pharo/issues/detail?id=6411 > > Issue 6427: use exitFailure in Pharo Kernel > http://code.google.com/p/pharo/issues/detail?id=6427 > > Issue 6426: Undeclared in ScriptLoader > http://code.google.com/p/pharo/issues/detail?id=6426 > > > > -- > Marcus Denker -- http://marcusdenker.de > >

July 19, 2012

Re: [Pharo-project] aggg!!!!

by Francois Stephany

+1 Don't be sorry Esteban you do an amzaing job! On 19/07/12 06:32, Sean P. DeNigris wrote: > > EstebanLM wrote >> >> I'm deeply sorry :S > > Sh*t happens. Great work and good catch :) > > -- > View this message in context: http://forum.world.st/aggg-tp4640708p4640720.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

July 19, 2012

Re: [Pharo-project] aggg!!!!

by Edgar J. De Cleene

On 7/19/12 10:12 AM, "Esteban Lorenzano" <estebanlm(a)gmail.com> wrote: > Hi, > > Ok, this morning I discovered an important bug in the release from yesterday: > FlatMessageListBrowser had a missing method, so there was no shout on message > lists. > Before everybody start to yell at me, and with reason, I silently fixed > yesterday's release and updated all links... now it is working as expected. > > I have to say that it was not my fault! I don't know when that method was lost > and since there were no reports about it (and the 1.4 version I was regularly > using was ok), I didn't see the problem until now... I'm deeply sorry :S > > Esteban Los genios tanvien ce hequiocan :=) Great job with the release and many thanks !!! Edgar

July 19, 2012