| Release | Resolved | Community Contributions |
| 0.5.1 12 May 2010 |
8 bugs |
Thanks to bugs filed by Jens Seidel and Chris Conway, Jeff Johnston fixed bugs in our Autotools component. Jeff also fixed bugs in our ChangeLog and libhover components and included the Autotools plugin documentation which was mistakenly missed in 0.5.0. Roland Grunberg fixed some OProfile bugs and committed a patch submitted by Lawrie Nichols in bug #296228. As well, our OProfile native fragment dropped its erroneously-licensed opxml binary; users will now need to rebuild on their system which will actually fix a few bugs people were seeing. |
| 0.5 18 March 2010 |
70 bugs |
Niels Thykier and Benjamin Drung provided many patches for eclipse-build and ran test builds to verify fixes and improvements. Anithra contributed the SystemTap dashboard and removed the SystemTap server dependency. Thanks to Jens Seidel and Roland Grunberg who helped test & fix SystemTap bugs. Jens also helped with testing our Autotools integration. |
| 0.4.1 21 Dec. 2009 |
5 bugs |
This was a bug-fix-only release, resolving some issues with Autotools and OProfile plugins. |
| 0.4 23 Nov. 2009 |
101 bugs |
Our Eclipse SDK build harness, eclipse-build, would be much worse off if it weren't for the patches and testing by Benjamin Drung, Matthias Klose, Marvin Schmidt, and Niels Thykier. Nick Boldt once again helped us with some release engineering issues. Thanks to users such as Jens Seidel, Andrew Gvozdev, and PurpleFloyd for reporting some key bugs against Autotools and testing the subsequent fixes. |
| 0.3 19 August 2009 |
113 bugs |
Jens Seidel helped with Autotools and Valgrind testing, filing important bugs. Alex Mueller guided the development of the manual control of the OProfile daemon. Nick Boldt once again helped us with our release engineering processes. Martin Gerhardy and Mat Booth helped getting the RPM specfile editor to work on Windows. Andrew Niefer and Kim Moir helped a lot with getting eclipse-build off the ground and with difficult problems. |
| 0.2.1 5 June 2009 |
1 bug |
Patrick Hofer and others notified us of a bug with our Valgrind components on Debian-based systems. |
| 0.2 11 May 2009 |
67 bugs |
Ed Swartz assisted in tracking down a UI blocker in the configure.ac editor. Pedro Saraiva pointed out a localization issue with the massif plugin. Uwe Stieber fixed a compilation problem with Eclipse 3.5, fixed the OProfile fragments, and illustrated an incorrect BREE. Jens Seidel and Ben Konrath both filed bugs with good test cases and helped track down problems. Uwe Stieber, Mikael Steen Springer, and Axel Mueller helped Kent Sebastian to improve the privilege escalation code for launching opxml on various Linux distributions. Nick Boldt helped improve our automated build process. |
| 0.1 23 Jan. 2009 |
11 bugs |
Alphonse van Assche contributed many fixes for our RPM specfile editor as well as integration of rpmlint error and warning parsing. Phil Muldoon contributed his Systemtap editor and helped with ChangeLog bug fixes. Kent Sebastian picked up Keith Seitz's work on OProfile and worked with Elliott Baron to create a framework for profiling tools. Elliott contributed his work on integrating the Valgrind suite of tools into the IDE. Alexander Kurtakov contributed many fixes to our RPM specfile editor as well as making the initial RPM Stubby work usable. Nick Boldt helped us immensely as we got our release engineering processes straightened out. Jeff Johnston contributed his work on integrating the GNU Autotools with the CDT. Jeff also contributed his work on bridging the gap between API documentation and the CDT's hover help with his libhover work. |
| pre-0.1 |
69 bugs |
Prior to our 0.1 release, Remy Chi Jian Suen helped us out with proper execution environments for our plugins among other things. Phil Muldoon contributed his ChangeLog plugin. Kyu Lee then contributed an editor for ChangeLog files. Keith Seitz contributed his OProfile integration plugins. Igor Foox helped out a great deal getting our RPM specfile editor started. |
Also see the New & Noteworthy for:
Linux Tools 0.1
Linux Tools 0.2.1
Linux Tools 0.3
Linux Tools 0.4
New in Linux Tools 0.5
|
Change to .autotools file |
The latest version of the Autotools plug-in has changed the format of the .autotools file to store configurations with their configuration id rather than name. In addition, the order of configuration options has been stabilized to a set order. |
|
|
|
|
Removed function/method support |
A fix has been made to the ChangeLog plug-in so it adds removed methods and function names to a prepared ChangeLog entry.
|
|
|
|
|
New SDK version |
Eclipse-build has been updated to build the new version of the Eclipse SDK 3.5.2. |
|
|
|
|
System libraries |
Eclipse-build has been extended to use system jars for external dependencies instead of the jars shipped with SDK. |
|
|
|
|
ECF |
ECF build is part of the bootstrapping step now allowing us to use the just built ecf instead of rebuilding them after the SDK build. |
|
|
|
|
Multi-threaded profiling |
Callgraph can now trace function calls in multi-threaded programs. No difference in terms of the user interface, but now when graphing Callgraph will automatically track which functions belong to which thread and display them accordingly.
|
|
|
|
|
Convert To DOT Language |
Eclipse Callgraph can now save graphs to the DOT language. In Eclipse Callgraph, click the main menu and choose File -& Save As, then choose an option to save parts of the graph or the whole graph as a .dot file. Graphs in DOT language can then be graphed or converted to other formats (e.g. PDF, PNG, etc.) by any of a large number of existing DOT parsing programs.
|
|
|
|
|
Code coverage |
GCov code coverage output files can now be visualized in Eclipse. An application compiled with "-fprofile-arc" "-ftest-coverage" will generate 2 coverage output files (*.gcda/*.gcno) for each source file of the program. Double clicking on one of these files provides an overview of coverage for the whole program. In addition, source files are annotated with lines covered their frequency of execution.
|
|
|
|
|
Improved Maven projects support |
Proper install for jars in a pom project and make use %{_mavenpomdir} macro.
|
|
|
|
|
Simplification |
Ability to generate gcj specific parts has been dropped. |
|
|
|
|
Robustness |
Use %global macro instead of %define. See here for details.
|
|
|
|
|
Download sources |
Sources defined in the spec file can be downloaded now from inside Eclipse.
|
|
|
|
|
SRPM Import |
SRPM import wizard creates RPM project directly instead of running the generic new project.
|
|
|
|
|
Wizards |
Wizards have been grouped in RPM category.
|
|
|
|
|
General editing |
|
|
|
|
|
SystemTap Dashboard |
The Dashboard Perspective is the most advanced part of SystemTap GUI. It is designed to allow users to browse and run prebuilt modules in order to see multiple graphs updating in sequence.The dashboard allows for visualizing specific system activities graphically. SystemTap dashboard |
|
|
|
|
Removed server dependency |
The SystemTap GUI server is now redundant. SystemTap scripts are executed using remote ssh. |
|
|
|
|
LTTng Integration |
The LTTng project aims at providing highly efficient tracing tools for Linux. Its tracers help tracking down performance issues and debugging problems involving multiple concurrent processes and threads. The scope of this project is to provide an Eclipse-based alternative to LTTV, a front-end that allows visualization and analysis of traces generated by LTTng tracers. Refer to the integrated help for a description of the initial features including the new LTTng perspective and views.
LTTng Perspective |
|
|
|