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

GOUBIER Thierry thierry.goubier at cea.fr
Wed Jul 18 13:59:26 EDT 2012

Yes. It would be easy to do.

How it would work as Jejak is now. Trace as it is, scan the trace with an AST visitor (or just the reference on all branches in the original code). Jejak provides: the probe writer for traces, an AST visitor to relate a trace event to the original source code, and trace visitors (for trace transformation and filtering).

De : pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] de la part de Frank Shearar [frank.shearar at gmail.com]
Date d'envoi : mercredi 18 juillet 2012 18:28
À : Pharo-project at lists.gforge.inria.fr
Objet : Re: [Pharo-project] [ANN] The Jejak Trace framework

On 18 July 2012 13:55, Goubier Thierry <thierry.goubier at cea.fr> wrote:
> 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 at 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?


More information about the Pharo-dev mailing list