On 01 Dec 2014, at 15:58, Alexandre Bergel <alexandre.bergel@me.com> wrote:

Would Hapao benefit from using reflectivity as it's intercession framework instead of using method wrappers? Maybe in such a way it can also instrument classes such as Array, Object���

May be. But I am wondering whether it will really solve the problem. I guess reflectivity is using the same kind of transformation as we do. 

What we do is to model recursion��� a link is active at a certain ���meta level���, calling the meta object switches the meta level, which means that

it will not take the link again ���> meta recursion is stopped.

In Java, the JVM provides an interface, to which you can connect a debugger. With such interface, you can literally profile anything. 

The idea is to integrate it with the VM (to some extend) via Sista next year.

Alexandre

On Mon, Dec 1, 2014 at 2:34 PM, Pavel Krivanek <pavel.krivanek@gmail.com> wrote:

Right. Some tests ended with out-of-memory errors or vm crash. One
problem was in a trait so I had to put all users of it on the
blacklist.

Cheers,
-- Pavel

2014-12-01 14:21 GMT+01:00 Alejandro Infante <alejandroinfante91@gmail.com>:
> Hapao works using method wrappers, and do some stuff for every method
> execution. If Hapao use something you are instrumenting, you are start
> looping endlessly. So blacklisted classes are classes you are not going to
> instrument.
>
> But, I was trying to understand all the classes you blacklisted, and I don���t
> understand why you have some tests blacklisted, any reason for them?
>
> Cheers,
> Alejandro
>
> On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito@gmail.com>
> wrote:
>
> ignorant question: What is a black listed class? :)
>
> On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek@gmail.com>
> wrote:
>>
>> Hi,
>>
>> I set the job for tests coverage testing of the mimimal Pharo using Hapao:
>>
>>
>> https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2.2-Hapao-Coverage-Test/
>>
>> To load results you should load ConfigurationOfSUnit and
>> ConfigurationOfKernelTests from Pharo/SystemConfigurations repository
>> into an image with Hapao. Then inspect:
>>
>> FLMaterializer materializeFromFileNamed: 'hapao.fuel'.
>>
>> Do not try to visualise it ;-)
>>
>> Currently blacklisted classes are:
>>
>> Array Association ArrayedCollection Behavior BlockClosure ByteSymbol
>> ByteString ClassDescription CompiledMethod Class Dictionary
>> Hapao2Package HashedCollection IdentityDictionary Integer LookupKey
>> FileStream Magnitude Object ProtoObject Process ProcessLocalVariable
>> ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage
>> SmalltalkImage SequenceableCollection Set Semaphore SmallInteger
>> Symbol String SourceFileArray VirtualMachine OCCompilerTest
>> SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest
>> BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest
>> LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod
>> S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage
>> S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method
>> S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin
>> S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack
>> S2StringNewPlugin S2TestException S2Tester S2TesterClass
>> S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB
>> S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod
>> S2pySenderStubPackage
>>
>> Cheers,
>> -- Pavel
>>
>
>