[Pharo-project] Idea for finding bugs/profiling...
Hi alex would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences. For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help. Stef
Another idea would be to be able to provide an expression and to know when in the trace this expression is false or true For example I would like to know when the classes are unloaded exactly. So I could run a test and ask tell me from which invocation this expression is false. And I would know immediately what is the expression correctly removing classes and I could compare. Stef On Oct 14, 2012, at 10:44 PM, Stéphane Ducasse wrote:
Hi alex
would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences.
For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help.
Stef
would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences.
For which tests and which applications? All the Pharo tests? That could easily be done if we stay away from tracing the kernel and collections. Method Wrapper would easily do the thing.
For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Oct 14, 2012, at 11:56 PM, Alexandre Bergel wrote:
would it not be possible to run and trace automatically the same tests in 1.4 and 2.0 and see the delta? because this would help us a lot of understand the differences.
It is for gofer tests.
For which tests and which applications? All the Pharo tests? That could easily be done if we stay away from tracing the kernel and collections. Method Wrapper would easily do the thing.
We should incrementally build ups new infrastructure. I'm thinking about object centric debugger for example.
For example, I trying to fix the Gofer unload behavior and I'm stepping step by step in 1.4 and 2.0. Having some support would really help.
Stef
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
participants (2)
-
Alexandre Bergel -
Stéphane Ducasse