Google Git
Sign in
eclipse / gerrit / www.eclipse.org / linuxtools / f3b35e5f8545a24a40614348c9047dc87da8ae9e / . / new / 0.7 / new.html
blob: 6a8b3fb2388dedaef1cd8b1d4dfa56e8a400fee2 [file] [log] [blame]
<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" 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.7<br>
<i>16 Feb 2011</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.7&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">
60 bugs</a></td>
<td bgcolor="#E0D0E6"><font size="1"> The LTTng team improved the visualization tools and performance. All help content is maintained in Eclipse.org wiki and with Mylyn Wikitext.
.spec file and changelog editors properly show/use Mylyn hyperlinks when bug reference is detected. </font></td>
</tr>
</table>
<hr>
<p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 0.7</span> </p>
<ul>
<li><a href="#autotools">GNU Autotools Support (1)</a></li>
<li><a href="#changelog">ChangeLog Tools (2)</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 (# of items for this area; comment out if none)</a></li> -->
<!-- <li><a href="#oprofile">OProfile Profiling (# of items for this area; comment out if none)</a></li> -->
<li><a href="#specfileeditor">RPM <tt>.spec</tt> Editor (2)</a></li>
<li><a href="#valgrind">Valgrind Profiling (1)</a></li>
<li><a href="#lttng">LTTng (4)</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>Error Detection</b></p>
</td>
<td valign="top" width="70%">
<p align="left">The Autotools configuration builder has been enhanced to recognize errors that occur in running the configure script and flag them in the console. In addition, these problems are noted in the Problems view as well.</p>
<img border="0" alt="Pkg-config Configure Error" src="images-0.7/autotools-pkgconfig-error.png">
<img border="0" alt="Problems View" src="images-0.7/autotools-problems.png">
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
</table>
<h2><a name="changelog">ChangeLog Tools</a></h2>
<table cellpadding="10" cellspacing="0">
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Removed Method Support</b></p>
</td>
<td valign="top" width="70%">
<p align="left">The ChangeLog plug-in has been fixed so that it will detect when methods are removed from a Java file and automatically generate a reference to the method. This functionality already existed for C/C++ functions/methods.
</p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Mylyn bug hyperlinks</b></p>
</td>
<td valign="top" width="70%">
<p align="left">The ChangeLog plug-in has been enhanced so it shows bug references as hyperlinks and allows opening them with Mylyn.
</p>
</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>Mylyn bug hyperlinks</b></p>
</td>
<td valign="top" width="70%">
<p align="left">The RPM .spec file editor plug-in has been enhanced so it shows bug references as hyperlinks and allows opening them with Mylyn.
</p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Error line matcher</b></p>
</td>
<td valign="top" width="70%">
<p align="left">The RPM .spec file editor plug-in has been enhanced to properly detect rpmbuild errors in build output and shows them as hyperlinks pointing to the line in the editor when rpmbuild reports it.
</p>
</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>Mac OSX Support</b></p>
</td>
<td valign="top" width="70%">
<p align="left">As Valgrind now officially supports Mac OSX, our Valgrind integration feature can now be installed
on OSX.
</p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
</table>
<h2><a name="lttng">LTTng</a></h2>
<table cellpadding="10" cellspacing="0">
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Histogram View</b></p>
</td>
<td valign="top" width="70%">
<p align="left">
The Histogram View layout has been improved. The larger histogram, at
the bottom, shows the events distribution over the whole trace.
The timetamps (sec.nanosec) correspond to the first and the last
events in the trace. The selected area corresponds to the current
time range window. When clicking in that viewer, the mouse wheel
can be used to zoom in/out and update the time range window.
<p>
The smaller histogram, on the top right of the view, is a zoom
of the current time range window. It also has timestamps on the
bottom that correspond to the time range. The scale of the
histogram (i.e. the number of events) is displayed on the right.
<p>
The three text fields keep track of, respectively, [1] the timestamp
of the currently selected event, [2] the time range window size, and
[3] the timestamp of the window center.
</p>
<img border="0" alt="Alt text for the image" src="images-0.7/LTTngHistogramView.png">
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Help re-vamped</b></p>
</td>
<td valign="top" width="70%">
<p align="left">
The LTTng Help was re-vamped base on the wiki-based LTTng User
Guide.
</p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Individual trace analysis</b></p>
</td>
<td valign="top" width="70%">
<p align="left">
It is now possible to bypass the experiment and to select an
individual trace for analysis. The trace can be selected from the
Traces folder or from an experiment folder (under Experiments).
</p>
</td>
</tr>
<tr>
<td colspan="2">
<hr>
</td>
</tr>
<tr>
<td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
<p align="right"><b>Performance Improvements</b></p>
</td>
<td valign="top" width="70%">
<p align="left">
Miscellaneous performance improvements. The current version runs
~20 times faster than the original delivery (which was definitely
not a speed demon...) and executes now in an acceptable time
compared to the C version of the visualizer.
</p>
</td>
</tr>
</table>
<h2>&nbsp;</h2>