| <table border="1" style="border-collapse: collapse" width="100%" id="table128" cellpadding="4" bordercolor="#FFFFFF"> |
| <tr> |
| <td bgcolor="#595791" width="7%" align="center"><b> |
| <font color="#FFFFFF" size="1">Release</font></b></td> |
| <td bgcolor="#595791" width="5%" align="center"><b> |
| <font color="#FFFFFF" size="1">Resolved |
| </font></b></td> |
| <td bgcolor="#595791" width="*" align="center"><b> |
| <font color="#FFFFFF" size="1">Community Contributions</font></b></td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#E0D0E6"><font size="1">0.3<br> |
| <i>19 August 2009</i></font></td> |
| <td bgcolor="#E0D0E6" align="center"> |
| <a href="https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&classification=Tools&product=Linux+Tools&target_milestone=0.3&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&known_name=0.3.0&query_based_on=0.3.0&field0-0-0=noop&type0-0-0=noop&value0-0-0"> |
| 77 bugs</a></td> |
| <td bgcolor="#E0D0E6"><font size="1"> |
| 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. |
| </font></td> |
| </tr> |
| </table> |
| |
| <hr> |
| |
| <p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 0.3</span> </p> |
| <ul> |
| <li><a href="#autotools">GNU Autotools Support (2)</a></li> |
| <li><a href="#eclipsebuild">Building the Eclipse SDK (1)</a></li> |
| <li><a href="#libhover">API Documentation Hover Help (1)</a></li> |
| <li><a href="#oprofile">OProfile Profiling (3)</a></li> |
| <li><a href="#specfileeditor">RPM <tt>.spec</tt> Editor (5)</a></li> |
| <li><a href="#systemtap">SystemTap Integration (2)</a></li> |
| <li><a href="#valgrind">Valgrind Profiling (6)</a></li> |
| </ul> |
| |
| <h2><a name="autotools">GNU Autotools Support</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Manual Reconfigure</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The newest Autotools now allows the user to manually rerun the configure script. The option is available in the Project menu. |
| </p> |
| <img border="0" alt="Reconfigure" src="images-0.3/reconfigure.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Tool Support</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The latest Autotools plugin adds support for the autoheader, autoreconf, and libtoolize tools in addition to the existing tools: aclocal, autoconf, and automake. Instead of displaying the results in a dialog, all Autotool invocation results are now displayed in the new Autotools console. Invoking the tools can be done from the Project->Invoke Autotools menu item and each tool's binary location can be specified in the Project->Properties->Autotools->Tools Settings tab. |
| </p> |
| <img border="0" alt="Autoreconf" src="images-0.3/autoreconf.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a name="eclipsebuild">Building the Eclipse SDK</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Full Build</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">This first release of eclipse-build is capable of building the Eclipse SDK solely with ant and a JDK. Eclipse 3.5 (I20090611-1540) builds fine with the source tarball provided by this project. The build is verified to succeed on Linux on x86, x86_64 and ppc architectures.<br/> |
| We encourage all Linux distributions to start using eclipse-build and get their Eclipse stack updated to the latest release. Let's share the work of integrating Eclipse Tools with Linux distributions!<br/> |
| Instructions for how to use eclipse-build to build the Eclipse SDK are kept <a href="http://wiki.eclipse.org/Linux_Tools_Project/Eclipse_Build">in the wiki</a>. |
| </p> |
| |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| <h2><a name="libhover">API Documentation Hover Help</a></h2> |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>C++ Support</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The new Libhover Libstdc++ feature adds C++ hover help for the libstdc++ library. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images-0.3/cpplibhover.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a name="oprofile">OProfile Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Manual Profiling</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Initially, OProfile would be launched when the target binary is executed and OProfile would terminate when the target binary exits. Now, via a control dialog, the OProfile daemon may be started and stopped at will for greater control and precision in profiling your applications. |
| </p> |
| <img border="0" alt="Manual Profiling Dialog" src="images-0.3/Screenshot-oprofile_manual_dialog.png"> |
| <img border="0" alt="Manual Profiling Launch Shortcut" src="images-0.3/Screenshot-oprofile_manual_shortcut.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Launch Test Coverage</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The launch plug-in's test coverage has improved significantly. |
| </p> |
| <img border="0" alt="Test Coverage Dialog" src="images-0.3/Screenshot-oprofile_launch_testcoverage.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Eclipse Help User Guide</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Linux Tools 0.3.0 release makes the <a href="http://wiki.eclipse.org/Linux_Tools_Project/OProfile/User_Guide">OProfile user guide</a> available via a link in the Eclipse Help System. |
| </p> |
| <img border="0" alt="Eclipse Help System With OProfile Item" src="images-0.3/Screenshot-oprofile_userhelp.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a name="specfileeditor">RPM <tt>.spec</tt> Editor</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Form based editor</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">An initial form based editor has been added. As well, support for a limited number of sections and tags is also provided. This initial version will form the basis for future work. |
| </p> |
| <img border="0" alt="Form based editor" src="images-0.3/specfile-form-editor.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Convert tabs to spaces </b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Support for replacing tabs with predefined number of spaces has been added to the editor. |
| </p> |
| <img border="0" alt="Tabs to spaces" src="images-0.3/specfile-tab-to-spaces.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>RPM project support</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">A wizard for creating RPM projects with standard rpmbuild directory structure has been added. |
| </p> |
| <img border="0" alt="RPM project" src="images-0.3/specfile-new-rpm-project.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Import SRPM</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The ability to import srpm files has been restored to the latest release. |
| </p> |
| <img border="0" alt="Import SRPM" src="images-0.3/specfile-import-srpm.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Export RPMS/SRPMS</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The ability to export RPM/SRPM files has also been restored to the latest release. |
| </p> |
| <img border="0" alt="Export RPM" src="images-0.3/specfile-export-rpms.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a name="systemtap">SystemTap Integration</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>SystemTap IDE</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Linux Tools 0.3.0 release now has an IDE for SystemTap. This includes a SystemTap editor and views that list available systemtap probes, systemtap functions and the kernel source code. |
| </p> |
| <img border="0" alt="SystemTap IDE" src="images-0.3/Screenshot-systemtap-1.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>SystemTap Graphs</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Support has been added to create custom graphs and view the output of SystemTap scripts as dynamic graphs. |
| </p> |
| <img border="0" alt="SystemTap Graph 1" src="images-0.3/Screenshot-systemtap-2.png"> |
| <img border="0" alt="SystemTap Graph 2" src="images-0.3/Screenshot-systemtap-3.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| |
| <h2><a name="valgrind">Valgrind Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Suppression File Editor</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">For Valgrind tools that output a series of errors, there can often |
| be a lot of noise — errors you are not interested in. Valgrind has the capability |
| of using Suppressions to ignore such errors. The syntax for defining Suppression Files |
| can be found <a href="http://www.valgrind.org/docs/manual/manual-core.html#manual-core.suppress">here</a>. |
| </p> |
| <p align="left"> |
| Now an editor for Valgrind Suppression files has been created and will be used for files ending with the |
| ".supp" extension. It features context-sensitive syntax highlighting (for instance only |
| highlighting the word "Memcheck" when used to define the tool relating to the Suppression), code folding and completion. |
| Completion is very useful to select from the full range of Memcheck Suppression types. |
| </p> |
| <p align="left"> |
| Currently only Memcheck is supported in the editor as it is the only tool of these plugins that uses Suppressions. |
| </p> |
| <img border="0" alt="Editing a Valgrind suppression file" src="images-0.3/valgrind-supp-editor.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>User Guide/Eclipse Help</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">A new documentation plugin, org.eclipse.linuxtools.valgrind.doc, has been created |
| that uses Mylyn <a href="http://wiki.eclipse.org/Mylyn/WikiText">WikiText</a>. This plugin fetches |
| a snapshot of the new <a href="http://wiki.eclipse.org/Linux_Tools_Project/Valgrind/User_Guide">user guide</a> on the Eclipse.org Wiki. |
| It then transforms it into HTML, DocBook XML and Eclipse Help. The plugin then contributes the Eclipse |
| Help via extension point to your workspace so you can view the user guide from the Help menu. |
| </p> |
| <img border="0" alt="Valgrind user guide in Eclipse Help" src="images-0.3/valgrind-eclipse-help.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>New Valgrind 3.4 Options</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Valgrind 3.4 brings a couple of new options to the Eclipse Valgrind plugins, the most interesting of which is the ability to track the origins of uninitialized values. This functionality |
| was frequently requested as the use of uninitialized memory may occur far later in the program than |
| its allocation. |
| </p> |
| <p align="left"> |
| The other new option is the ability to set the stack size for the program's main thread. |
| Valgrind by default requests the smaller of 16MB and the current ulimit value. For programs that |
| require more stack space than this, you can now specify what is needed. |
| </p> |
| <p align="left"> |
| New version checking code allows these options to be available to users with Valgrind 3.4 installed, |
| and hidden from those with a lesser version. |
| </p> |
| <img border="0" alt="Demonstrating Valgrind 3.4's track-origins option" src="images-0.3/valgrind-track-origins.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Fatal Error Handling</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">On occasion, fatal runtime errors may occur in your program |
| that force Valgrind to exit. Before exiting, the Valgrind Core will output detailed |
| information about the problem. Examples include exiting from a signal such as |
| a Segmentation Fault or Floating Point Exception; or being given an invalid suppression file. |
| </p> |
| <p align="left"> |
| In the case of a program-ending signal, there may still be useful output from Valgrind |
| up until that point in execution. For Memcheck, the tool's output coincides with |
| any output from the Valgrind core resulting in all errors being reported in the same |
| viewer — called the Valgrind Commentary pane. |
| </p> |
| <img border="0" alt="Encountering a segmentation fault running Memcheck" src="images-0.3/valgrind-memcheck-segv.png"> |
| <p align="left"> |
| For non-error reporting tools (Massif, Cachegrind), the fatal error will still appear in the |
| Valgrind Commentary pane, which is usually not used for Massif and Cachegrind. Switching to the |
| normal tool output is done from the Valgrind view's menu. |
| </p> |
| <img border="0" alt="Switching to Massif's tool output after encountering a segmentation fault" src="images-0.3/valgrind-massif-segv.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Export Massif Chart</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The allocation chart produced by the Massif plugin can now |
| be exported as an <a href="http://en.wikipedia.org/wiki/Scalable_Vector_Graphics">SVG</a>. |
| </p> |
| <img border="0" alt="Exporting the Massif chart as an SVG image" src="images-0.3/valgrind-svg-chart.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Minimum Supported Version Checking</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The minimum supported version for Valgrind is 3.3.0. Attempting to |
| use a lesser version in the past would result in unexpected behaviour. Now the problem |
| is clearly identifiable by an error dialog displaying your installed version and the |
| minimum version supported. |
| </p> |
| <img border="0" alt="Attempting to launch with Valgrind < 3.3.0" src="images-0.3/valgrind-old-version.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| |
| <h2> </h2> |
