Eclipse Trace Compass 3.3.0 Release Review

Type
Release
State
Successful
End Date of the Review Period

Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.

Release

3.3.0

Description

Trace Compass 3.3.0 is a minor release that ships with the Oxygen.3 update release.

This release will be part of Oxygen.3.

 

API Certification

The project leadership certifies that the APIs in this release are "Eclipse Quality".

Architectural Issues

The release is a small increment of our previous 3.2.0/Oxygen.2 update release. 

There are no architectural changes for the core framework.

The data-driven analysis internal design has been rewritten to separate compilation unit and execution. This allows for better validation of the XML analysis.

More support for the provisional Data Provider APIs have been provided for both XY views and Time Graph views to decouple UI and  Core components. Several views have been updated to this new APIs. The support in other views will be gradually added. The APIs will be made public once all views are migrated.

 

Security Issues

There are no security issues.

Non-Code Aspects

Trace Compass documentation is kept up-to-date for added and changed features. The developer and user guides are available as Eclipse help plug-ins and are part of the installable features. The latest released versions are also available on the Eclipse Foundation's web page.

End of Life

We have no end-of-life issues to discuss at this time.

A few API has been deprecated. New APIs have been added for later replacement. They will be removed in the 4.0 release for Photon.

Standards

Trace Compass comes with multipe built-in trace parsers for the following standard:

  • Common Trace Format (CTF) - v1.8.2

    • Linux LTTng kernel traces

    • Linux LTTng-UST userspace traces which can come from proprietary software or open source eg. Mir, MariaDB, QEMU traces

    • Other traces in CTF, e.g. Linux Perf traces (CTF), Bare metal traces (CTF), Hardware traces (e.g. IEEE Nexus 5001 CTF conversion).

  • GDB traces for debugging

  • Best Trace Format for OSEK

  • The libpcap (PAcket CAPture) format, for network traces

Trace Compass provides a remote tracer control for LTTng Kernel and UST Tracers for configuring of trace sessions. It supports the MI versions 2.0 and 3.0.

For the integration of the command-line analysis Trace Compass is able to consume analysis results specified by the LTTng Analysis Machine Interface.

Communities
  • 9 active committers from 3 different organizations

  • Trace Compass can be setup using Oomph.

  • User interaction via Bugzilla, IRC chat (#tracecompass) and mailing list (tracecompass-dev@eclipse.org)

  • Bugzilla has been used for planning and bug tracking

  • Centralized update site and download page for the standalone RCP

  • Strong relationship with the LTTng project. Project members interact with this community via mailing list (lttng-dev@lists.lttng.org).

  • Trace Compass is part of the Eclipse C/C++ EPP. One committer is also committer in CDT.

  • Trace Compass has been the preferred Trace Analysis Tool for students as part of the trace research projects with the Polytechnique Montreal university. Many new features and enhancements for Trace Compass have been a direct outcome of  the reseach projects. See below for a link to the current active research track: