| <table border="1" style="border-collapse: collapse" id="table128" cellpadding="4" bordercolor="#FFFFFF"> |
| <tr> |
| <td bgcolor="#595791" width="7%" align="center"><b> |
| <font color="#FFFFFF">Release</font></b></td> |
| <td bgcolor="#595791" width="5%" align="center"><b> |
| <font color="#FFFFFF">Resolved |
| </font></b></td> |
| <td bgcolor="#595791" width="*" align="center"><b> |
| <font color="#FFFFFF">Community Contributions</font></b></td> |
| </tr> |
| |
| <tr> |
| <td bgcolor="#E0D0E6">2.1<br> |
| <i>27 Sept 2013</i></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=2.1&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&field0-0-0=noop&type0-0-0=noop&value0-0-0"> |
| 38 bugs</a></td> |
| <td bgcolor="#E0D0E6">Minor release containing OPerf support, SystemTap editor upgrades, LTTng upgrades, in addition to bug fixes.</td> |
| </tr> |
| </table> |
| |
| <hr> |
| |
| <p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 2.1</span> </p> |
| <ul> |
| <!-- <li><a href="#changelog">ChangeLog Tools (# of items for this area; comment out if none)</a></li> --> |
| <!-- <li><a href="#eclipsebuild">Building the Eclipse SDK (# of items for this area; comment out if none)</a></li> --> |
| <!-- <li><a href="#gprof">GProf support (# of items for this area; comment out if none)</a></li> --> |
| <li><a href="#libhover">API Documentation Hover Help (1)</a></li> |
| <li><a href="#lttng">LTTng (7)</a></li> |
| <li><a href="#oprofile">OProfile Profiling (1)</a></li> |
| <li><a href="#perf">Perf Profiling (1)</a></li> |
| <li><a href="#rpmstubby">RPM Stubby (4)</a></li> |
| <li><a href="#specfileeditor">RPM <tt>.spec</tt> Editor (4)</a></li> |
| <li><a href="#systemtap">Systemtap Editor (1)</a></li> |
| <!-- <li><a href="#systemtapprofiling">Systemtap-based Profiling (# of items for this area; comment out if none)</a></li> --> |
| <!-- <li><a href="#valgrind">Valgrind Profiling (1)</a></li> --> |
| </ul> |
| |
| <!-- |
| <h2><a id="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>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <!-- |
| <h2><a id="changelog">ChangeLog Tools</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <!-- |
| <h2><a id="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>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <!-- |
| <h2><a id="gprof">GProf Integration</a></h2> |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <h2><a id="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>Devhelp regeneration on start-up</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Libhover Devhelp support has been enhanced so that the devhelp documentation is parsed |
| upon start-up of Eclipse. This enables devhelp selections immediately instead of waiting until the end-user manually schedules a |
| regeneration of the documentation in Libhover binary format. |
| </p> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <!-- LTTng --> |
| |
| <h2><a id="lttng">Linux Tracing Toolkit</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Configurable Time Zone Preference</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The time zone preference has been added to the time format preference page. |
| <br/> |
| <br/> |
| Refer to the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide#Timestamp_formatting">User Guide</a> |
| for detailed information time format preferences. |
| </p> |
| <img alt="Time Format Preferences" src="images/lttng_tmfTimestampFormatPage.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Support for Time Range Selection in Tracing Views</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">It is now possible to select a time range in the |
| tracing views instead of selecting just a single time. This |
| information is broadcasted using the time synchronization signal |
| so that relevant views update their selection. Also the selected |
| start time, end time and time delta is displayed in the status |
| line of the worbench. The time range selection is added |
| in the Control Flow view, Resources view and Histogram view. |
| The Events table also allows the selection of an event range. |
| The Statistics view now displays the number of events for |
| the selected time range. |
| <br/> |
| <br/> |
| Refer to the views sections of the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide">User Guide</a> |
| for detailed information about this feature. |
| </p> |
| <img alt="Time Range Selection" src="images/lttng_timeSelection.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Display of Execution Flow in Control Flow View</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Control Flow view now provides arrows to follow the |
| switching of CPU execution across processes. The arrows can be |
| followed in forward and backward direction by using the corresponding |
| buttons of the coolbar. The display of the arrow disabled by using the |
| Hide button of that view. |
| <br/> |
| <br/> |
| Refer to the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide#Control_Flow_View">User Guide</a> |
| for detailed information on this view and its usage. |
| </p> |
| <img alt="Process Flow" src="images/lttng_controlFlowViewArrows.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Support for LTTng Tools v2.2</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Control view now supports version v2.2 of |
| LTTng Tools. It is now possible to configure |
| <ul> |
| <li>UST buffers per user ID (per UID buffers)</li> |
| <li>the metadata channel including configuration of the timer for |
| periodic flush of the sub-buffers</li> |
| <li>file size and number of files to be written per channel |
| (file rotation)</li> |
| </ul> |
| <br/> |
| Refer to the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide#LTTng_Tracer_Control">User Guide</a> |
| for detailed information on the LTTng Tracer Control and its usage. |
| </p> |
| <img alt="Channel Configuration" src="images/lttng_createChannelDialog.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Highlight of Attribute Changes in State System |
| Explorer</li></b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The State System Explorer now hightlights the |
| changes of states when changing the current time selection. |
| <br/> |
| <br/> |
| Refer to the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide#State_System_Explorer_View">User Guide</a> |
| for detailed information on the State System Explorer and its |
| usage. |
| </p> |
| <img alt="State System Explorer" src="images/lttng_highlightedStateSystemExplorer.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Display of Trace Properties in the |
| Properties view</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The Eclipse's Properties view now shows also |
| additional trace properties such as CTF environment variables. |
| <br/> |
| <br/> |
| Refer to the <a href="http://wiki.eclipse.org/index.php/Linux_Tools_Project/LTTng2/User_Guide#Properties_View">User Guide</a> |
| for detailed information about the Properties view and displayed trace properties. |
| </p> |
| <img alt="Trace Properties" src="images/lttng_traceProperties.png"/> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Improved GUI Responsiveness</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The GUI reponsiveness has been improved when |
| processing multiple concurrent request while indexing a trace. |
| The updated request scheduler now ensures that each concurrent |
| request gets sufficient execution time and doesn't have to wait |
| for other requests of the same or higher priority to finish. |
| </p> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Framework Improvements</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| <ul> |
| <li>Introduced abstract Time Graph Widget classes to make it easier |
| for developers to create time graph views such as the |
| Control Flow view |
| </li> |
| <li>The Time Graph Widget now support the creation of links |
| between time graph entries and to draw arrows between events. This |
| has been used in the Control Flow view to follow CPU execution |
| across processes. |
| </li> |
| </ul> |
| </p> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a id="oprofile">OProfile Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>OPerf Support</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The OProfile plug-in has been enhanced to allow the end-user to use the new OPerf support added to OProfile. OPerf allows the end-user to profile without requiring root access. This eliminates the need for running a pre-installation script before running OProfile. |
| </p> |
| <img border="0" alt="OPerf Selection" src="images/operfSelection.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a id="perf">Perf Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Stat Diff View Improvements</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| The Stat Diff View shows the differences between two perf-stat reports in a view. |
| In addition it is now possible to view the individual reports used to form |
| the diff from the view |
| by selecting the 'Show Old Statistics' or 'Show New Statistics' buttons. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/perf_stat_diff_switch.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a id="rpmstubby">RPM Stubby</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>RPMStubby Menu</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The menu has been modified to allow the use of RPMStubby to stub out and make a <tt>.spec</tt> file out of Perl makefiles, Ruby gems, and Python eggs. |
| </p> |
| <img border="0" alt="RPMStubby menu" src="images/rpmstubby_menu.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Generate Perl <tt>.spec</tt> file stub</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| Perl makefiles contain a lot of information that could be used to package them as an RPM. The Perl stubby generator does exactly that by |
| generating a stubbed out <tt>.spec</tt> file template from the <tt>.PL</tt> file. |
| </p> |
| <p align="left"> |
| More information on the guidelines for this procedure can be viewed at <a href="https://fedoraproject.org/wiki/Packaging:Perl">Perl Packaging Guidelines</a>. |
| </p> |
| <img border="0" alt="Perl Makefile.PL Stubbed Specfile" src="images/rpmstubby_perlStub.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Generate Ruby <tt>.spec</tt> file stub</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| Ruby gems contain a lot of information that could be used to package them as an RPM. The Ruby stubby generator does exactly that by |
| generating a stubbed out <tt>.spec</tt> file template from the <tt>.gemspec</tt> file. |
| </p> |
| <p align="left"> |
| More information on the guidelines for this procedure can be viewed at <a href="https://fedoraproject.org/wiki/Packaging:Ruby">Ruby Packaging Guidelines</a>. |
| </p> |
| <img border="0" alt="Ruby Gemspec Stubbed Specfile" src="images/rpmstubby_rubyStub.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Generate Python <tt>.spec</tt> file stub</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| Python eggs contain a lot of information that could be used to package them as an RPM. The Python stubby generator does exactly that by |
| generating a stubbed out <tt>.spec</tt> file template from the <tt>setup.py</tt> file. |
| </p> |
| <p align="left"> |
| More information on the guidelines for this procedure can be viewed at <a href="https://fedoraproject.org/wiki/Packaging:Python">Python Packaging Guidelines</a>. |
| </p> |
| <img border="0" alt="Python Setup.Py Stubbed Specfile" src="images/rpmstubby_pythonStub.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a id="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>RPM Menu</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The menu has been modified to allow convenient access to the <b>Download Sources</b> and <b>Prepare Sources</b> functionality on the <tt>.spec</tt> file. |
| </p> |
| <img border="0" alt="RPM Menu" src="images/rpm_menu.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Download sources for a <tt>.spec</tt> file</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| The RPM <tt>.spec</tt> editor now supports being able to download the sources for the <tt>.spec</tt> file. |
| </p> |
| <p align="left"> |
| Downloading sources will attempt to download from the source urls within the <tt>.spec</tt> file. If the sources already exist within the current project, then Download Sources |
| will automatically overwrite the existing sources. |
| </p> |
| <img border="0" alt="Downloading Sources from RPM Specfile" src="images/rpm_downloadSources.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Prepare sources for a <tt>.spec</tt> file</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| The RPM <tt>.spec</tt> editor now supports being able to prepare the sources for the <tt>.spec</tt> file. |
| </p> |
| <p align="left"> |
| Preparing sources will attempt to download the source files before it executes the %prep section. |
| </p> |
| <p align="left">Refer to <a href="http://rpm.org/max-rpm-snapshot/ch-rpm-b-command.html#S2-RPM-B-COMMAND-BP-OPTION">Maximum RPM - Executing %prep</a> |
| </p> |
| <img border="0" alt="Preparing Sources from RPM Specfile" src="images/rpm_prepareSources.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Create patches that do not exist</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">RPM now supports creation of patch files by holding Ctrl then hovering and left clicking on a patch file that does not exist within the project that the specfile belongs to. The newly created file also follows the RPM Project layout and will place it accordingly</p> |
| <p align="left"> |
| The default editor for the file will open immediately after successful creation of the patch file. |
| </p> |
| <img border="0" alt="Ctrl + hovering over a non-existent Patch file" src="images/rpm_createPatchesHyperlink.png"> |
| <br> |
| <img border="0" alt="Opening of text editor when Patch is created successfully" src="images/rpm_createdPatch.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <h2><a id="systemtap">Systemtap Integration</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Enhanced SystemTap Editor Formatting</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">The SystemTap editor has been enhanced with regards to formatting. Auto indent capability has been added for new lines and the editor supports indent correction of either a single line or selected lines via the Ctrl+I short-cut. Comments can be added/removed via CTRL+/. In addition, the editor has been improved with regards to auto-completed characters to match the behaviour of existing editors such as the C/C++ editor. For example, if the user starts a string via a double-quote, the editor automatically adds the closing double-quote for the end-user and recognizes when the user unnecessarily types the closing double-quote again. |
| </p> |
| <img border="0" alt="SystemTap Editor" src="images/SystemTapEditor.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| |
| <!-- |
| <h2><a id="systemtapprofiling">Systemtap-based Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Short Description</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left">Longer description. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/image.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <!-- |
| <h2><a id="valgrind">Valgrind Profiling</a></h2> |
| |
| <table cellpadding="10" cellspacing="0"> |
| <tr> |
| <td align="left" valign="top" width="15%" bgcolor=#E0D0E6> |
| <p align="right"><b>Clear Valgrind plugin error markers after build</b></p> |
| </td> |
| <td valign="top" width="70%"> |
| <p align="left"> |
| Once the Valgrind plugin is run on an application, error markers may appear in the 'Problems' |
| view as well as on the problematic lines of source code. These markers are now cleared |
| automatically after a user-initiated build. |
| </p> |
| <img border="0" alt="Alt text for the image" src="images/valgrind_error_markers.png"> |
| </td> |
| </tr> |
| <tr> |
| <td colspan="2"> |
| <hr> |
| </td> |
| </tr> |
| </table> |
| --> |
| |
| <h2> </h2> |
