<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="#FAF7FB">1.2.1<br>
		<i>22 Feb 2013</i></td>
		<td bgcolor="#FAF7FB" 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=1.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">
		6 bugs</a></td>
		<td bgcolor="#FAF7FB">This was a minor bug-fix-only release that fixed an LTTng exception issue from 1.2, added scroll-bars to the Perf options page, fixed the ChangeLog User Guide, plus made some additional release engineering clean-ups.</td>
	</tr>
	<tr>
		<td bgcolor="#E0D0E6"><font size="1">1.2<br>
		<i>20 Nov 2012</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=1.2&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">
		49<br>
		bugs</font></a></td>
		<td bgcolor="#E0D0E6"><font size="1">In addition to minor bug-fixes, this release contains the new profiling unification framework which simplifies profiling for end-users.  As well, the SystemTap UI has undergone a major clean-up both for functionality and ease of use.</font></td>
	</tr>
</table>

<hr>

<p><span style="font-weight: 700; background-color: #E0D0E6">New in Linux Tools 1.2</span> </p>
<ul>
<li><a href="#profiling">Profiling Framework (1)</a></li>
<li><a href="#gcov">GCov support (1)</a></li>
<li><a href="#gprof">GProf support (1)</a></li>
<li><a href="#oprofile">OProfile Profiling (1)</a></li>
<li><a href="#perf">Perf Integration (1)</a></li>
<li><a href="#systemtap">SystemTap Editor (2)</a></li>
<li><a href="#valgrind">Valgrind Profiling (1)</a></li>
</ul>

<!-- Profiling Framework -->
<h2><a name="profiling">Profiling Framework</a></h2>

<table cellpadding="10" cellspacing="0">
        <tr>
            <td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
            <p align="right"><b>Profiling Unification</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">The Profiling Framework has been modified to add profiling categories which group various profiling tools that overlap in functionality.  There are three categories to start with: Timing, Memory, and Coverage and additional categories can be added in the future.  Each category has a Profiling Launch short-cut whereby the user can kick off a profiling session via a single click.  Each category has a default tool to use which includes default parameters.  For example, a user could select to do a Profile Timing run and this will end up using whatever profiling timing tool is set up as default.  The default can be changed via workspace preferences or over-ridden for a project via its properties.  For more details, see the <a href="http://wiki.eclipse.org/Linux_Tools_Project/Profiling/User_Guide">Profiling User's Guide</a>.
            </p>
            <img border="0" alt="C/C++ Profiling Categories" src="images/LinuxToolsProfilingPreferences.png">
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>

<!-- GCov -->
<h2><a name="gcov">GCov Integration</a></h2>

<table cellpadding="10" cellspacing="0">
        <tr>
            <td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
            <p align="right"><b>GCov Launch Support</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">With the new Profiling Unification framework, profiling tools are categorized into one of the three default categories: Timing, Memory, and Coverage.  GCov has been categorized into the Coverage category and as such can now be launched from the Profile Coverage launch short-cut.  The launch short-cut will run the executable, gather the coverage data, and then open the GCov viewer.  In the past, an end-user would have to run the executable manually and double-click on coverage data files created.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>

<!-- GProf -->
<h2><a name="gprof">GProf Integration</a></h2>

<table cellpadding="10" cellspacing="0">
        <tr>
            <td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
            <p align="right"><b>GProf Launch Support</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">Like GCov, GProf is part of the new Profiling Unification framework.  GProf is categorized in the Timing category along with Perf, OProfile, and Callgraph.  Also like GCov, it is now possible to launch GProf using the Profile Timing launch short-cut.  In the past, users had to double-click on the gmon.out file for the project.  The profiling launch short-cut will run the executable and will open the GProf view automatically for gmon.out, if created.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>

<!-- OProfile -->
<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>New Profiling Framework</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">OProfile has been added to the profiling tools in the new profiling unification framework.  It has been added to the Profile Timing category along with Perf, GProf, and Callgraph.  In addition to profiling an application via the direct OProfile launch short-cut, the Profile Timing short-cut can be used with OProfile being selected as the timing tool to use.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>


<!-- Perf Plugin -->
<h2><a name="perf">Perf Integration</a></h2>

<table cellpadding="10" cellspacing="0">
        <tr>
            <td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
            <p align="right"><b>New Profiling Framework</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">Perf has been added to the profiling tools in the new profiling unification framework.  It has been added to the Profile Timing category along with OProfile, GProf, and Callgraph.  In addition to profiling an application via the direct Perf launch short-cut, the Profile Timing short-cut can be used with Perf being selected as the timing tool to use or simply by default since Perf is the Timing category default tool.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>

<!-- SystemTap -->
<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 Launch Configuration</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">Systemtap scripts can now be run through the context menu by right-clicking on the
	      in the editor or on the file in the project explorer and selecting 'Run As' -> 'Systemtap Script'.
	      Alternatively you can select  'Run As' -> 'Run Configurations...'. This will bring up the Run Configurations
	      dialog which now has an entry for SystemTap. The screen shot below shows the details of that dialog.
            <img border="0" alt="SystemTap Launch Configuration" src="images/SystemTapLaunchConfiguration.png">
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
        <tr>
            <td align="left" valign="top" width="15%" bgcolor=#E0D0E6>
            <p align="right"><b>Miscellaneous Improvements</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">
	      The way probe points are collected from installed SystemTap
	      application was improved making it faster and less error prone.
	      In addition there were numerous bug fixes and stability improvements.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>

<!-- Valgrind -->
<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>New Profiling Framework</b></p>
            </td>
            <td valign="top" width="70%">
            <p align="left">The set of Valgrind tools has been added to the new profiling unification fframework under the Memory category.  The list of tools includes Cachegrind, Memcheck, Helgrind, and Massif.  There already exists a direct profiling launch short-cut for Valgrind, but this defaults to use Memcheck unless the end-user modifies the Profiling Configuration to set the tool otherwise.  With the new framework, the user can choose the Valgrind tool ahead of time and invoke the Profile Memory launch short-cut directly without having to perform the extra step of modification.
            </p>
            </td>
        </tr>
        <tr>
            <td colspan="2">
            <hr>
            </td>
        </tr>
</table>


<h2>&nbsp;</h2>