<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html xmlns:fn="http://www.w3.org/2005/02/xpath-functions">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<link rel="stylesheet" href="../../../../doc/otp_doc.css" type="text/css">
<title>Erlang -- Runtime_Tools Release Notes</title>
</head>
<body bgcolor="white" text="#000000" link="#0000ff" vlink="#ff00ff" alink="#ff0000"><div id="container">
<script id="js" type="text/javascript" language="JavaScript" src="../../../../doc/js/flipmenu/flipmenu.js"></script><script id="js2" type="text/javascript" src="../../../../doc/js/erlresolvelinks.js"></script><script language="JavaScript" type="text/javascript">
<!--
function getWinHeight() {
var myHeight = 0;
if( typeof( window.innerHeight ) == 'number' ) {
//Non-IE
myHeight = window.innerHeight;
} else if( document.documentElement && ( document.documentElement.clientWidth ||
document.documentElement.clientHeight ) ) {
//IE 6+ in 'standards compliant mode'
myHeight = document.documentElement.clientHeight;
} else if( document.body && ( document.body.clientWidth || document.body.clientHeight ) ) {
//IE 4 compatible
myHeight = document.body.clientHeight;
}
return myHeight;
}
function setscrollpos() {
var objf=document.getElementById('loadscrollpos');
document.getElementById("leftnav").scrollTop = objf.offsetTop - getWinHeight()/2;
}
function addEvent(obj, evType, fn){
if (obj.addEventListener){
obj.addEventListener(evType, fn, true);
return true;
} else if (obj.attachEvent){
var r = obj.attachEvent("on"+evType, fn);
return r;
} else {
return false;
}
}
addEvent(window, 'load', setscrollpos);
//--></script><div id="leftnav"><div class="innertube">
<img alt="Erlang logo" src="../../../../doc/erlang-logo.png"><br><small><a href="index.html">Reference Manual</a><br><a href="release_notes.html">Release Notes</a><br><a href="../pdf/runtime_tools-1.8.9.pdf">PDF</a><br><a href="../../../../doc/index.html">Top</a></small><p><strong>Runtime_Tools</strong><br><strong>Release Notes</strong><br><small>Version 1.8.9</small></p>
<br><a href="javascript:openAllFlips()">Expand All</a><br><a href="javascript:closeAllFlips()">Contract All</a><p><small><strong>Chapters</strong></small></p>
<ul class="flipMenu" imagepath="../../../../doc/js/flipmenu"><li id="loadscrollpos" title="Runtime_Tools Release Notes" expanded="true">Runtime_Tools Release Notes<ul>
<li><a href="notes.html">
Top of chapter
</a></li>
<li title="Runtime_Tools 1.8.9"><a href="notes.html#id61643">Runtime_Tools 1.8.9</a></li>
<li title="Runtime_Tools 1.8.8"><a href="notes.html#id61709">Runtime_Tools 1.8.8</a></li>
<li title="Runtime_Tools 1.8.7"><a href="notes.html#id57934">Runtime_Tools 1.8.7</a></li>
<li title="Runtime_Tools 1.8.6"><a href="notes.html#id62949">Runtime_Tools 1.8.6</a></li>
<li title="Runtime_Tools 1.8.5"><a href="notes.html#id62980">Runtime_Tools 1.8.5</a></li>
<li title="Runtime_Tools 1.8.4.1"><a href="notes.html#id63010">Runtime_Tools 1.8.4.1</a></li>
<li title="Runtime_Tools 1.8.4"><a href="notes.html#id58120">Runtime_Tools 1.8.4</a></li>
<li title="Runtime_Tools 1.8.3"><a href="notes.html#id58149">Runtime_Tools 1.8.3</a></li>
<li title="Runtime_Tools 1.8.2"><a href="notes.html#id56501">Runtime_Tools 1.8.2</a></li>
<li title="Runtime_Tools 1.8.1"><a href="notes.html#id56532">Runtime_Tools 1.8.1</a></li>
<li title="Runtime_Tools 1.8"><a href="notes.html#id56566">Runtime_Tools 1.8</a></li>
<li title="Runtime_Tools 1.7.3"><a href="notes.html#id56633">Runtime_Tools 1.7.3</a></li>
<li title="Runtime_Tools 1.7.2"><a href="notes.html#id56663">Runtime_Tools 1.7.2</a></li>
<li title="Runtime_Tools 1.7.1"><a href="notes.html#id56735">Runtime_Tools 1.7.1</a></li>
<li title="Runtime_Tools 1.7"><a href="notes.html#id56882">Runtime_Tools 1.7</a></li>
<li title="Runtime_Tools 1.6.8"><a href="notes.html#id64799">Runtime_Tools 1.6.8</a></li>
<li title="Runtime_Tools 1.6.7"><a href="notes.html#id64835">Runtime_Tools 1.6.7</a></li>
<li title="Runtime_Tools 1.6.6"><a href="notes.html#id64887">Runtime_Tools 1.6.6</a></li>
<li title="Runtime_Tools 1.6.5"><a href="notes.html#id64979">Runtime_Tools 1.6.5</a></li>
<li title="Runtime_Tools 1.6.4"><a href="notes.html#id65011">Runtime_Tools 1.6.4</a></li>
<li title="Runtime_Tools 1.6.3"><a href="notes.html#id65043">Runtime_Tools 1.6.3</a></li>
<li title="Runtime_Tools 1.6.2"><a href="notes.html#id65091">Runtime_Tools 1.6.2</a></li>
<li title="Runtime_Tools 1.6.1"><a href="notes.html#id65124">Runtime_Tools 1.6.1</a></li>
<li title="Runtime_Tools 1.6"><a href="notes.html#id65176">Runtime_Tools 1.6</a></li>
<li title="Runtime_Tools 1.5.1.1"><a href="notes.html#id65189">Runtime_Tools 1.5.1.1</a></li>
<li title="Runtime_Tools 1.5.1"><a href="notes.html#id65226">Runtime_Tools 1.5.1</a></li>
</ul>
</li></ul>
</div></div>
<div id="content">
<div class="innertube">
<h1>1 Runtime_Tools Release Notes</h1>
<p>This document describes the changes made to the Runtime_Tools
application.</p>
<h3><a name="id61643">1.1
Runtime_Tools 1.8.9</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
Change the module-level docs to give complete
step-by-step instructions for using the `dyntrace:p()`
trace function. (Thanks to Scott Lystig Fritchie)</p>
<p>
Own Id: OTP-10141</p>
</li>
<li>
<p>
Add 1024 separate USDT probes to dyntrace.erl and
dyntrace.c (Thanks to Scott Lystig Fritchie)</p>
<p>
Own Id: OTP-10143</p>
</li>
<li>
<p>
Relocate bodies of DTrace probes to the statically-linked
VM.</p>
<p>
Due to various operating systems (in both the DTrace and
SystemTap worlds) not fully supporting DTrace probes (or
SystemTap-compatibility mode probes) in shared libraries,
we relocate those probes to the statically-linked virtual
machine. This could be seen as pollution of the pristine
VM by a (yet) experimental feature. However:</p>
<p>
1. This code can be eliminated completely by the C
preprocessor. 2. Leaving the probes in the dyntrace NIF
shared library simply does not work correctly on too many
platforms. *Many* thanks to Macneil Shonle at Basho for
assisting when my RSI-injured fingers gave out. (note:
Solaris 10 and FreeBSD 9.0-RELEASE can take a long time
to compile)</p>
<p>
Own Id: OTP-10189</p>
</li>
</ul>
<h3><a name="id61709">1.2
Runtime_Tools 1.8.8</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The DTrace source patch from Scott Lystig Fritchie is
integrated in the source tree. Using an emulator with
dtrace probe is still not supported for production use,
but may be a valuable debugging tool. Configure with
--with-dynamic-trace=dtrace (or
--with-dynamic-trace=systemtap) to create a build with
dtrace probes enabled. See runtime_tools for
documentation and examples.</p>
<p>
Own Id: OTP-10017</p>
</li>
</ul>
<h3><a name="id57934">1.3
Runtime_Tools 1.8.7</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
Earlier dbg:stop only did erlang:trace_delivered and did
not flush the trace file driver. Therefore there could
still be trace messages that were delivered to the driver
(guaranteed by erlang:trace_delivered) but not yet
written to the file when dbg:stop returned. Flushing is
now added on each node before the dbg process terminates.</p>
<p>
Own Id: OTP-9651</p>
</li>
<li>
<p>
File handles created by the trace_file_drv driver was
inherited to child processes. This is now corrected.</p>
<p>
Own Id: OTP-9658</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Erlang/OTP can now be built using parallel make if you
limit the number of jobs, for instance using '<span class="code">make
-j6</span>' or '<span class="code">make -j10</span>'. '<span class="code">make -j</span>' does not
work at the moment because of some missing
dependencies.</p>
<p>
Own Id: OTP-9451</p>
</li>
<li>
<p>
Two new built-in trace pattern aliases have been added:
caller_trace (c) and caller_exception_trace (cx). See the
dbg:ltp/0 documentation for more info.</p>
<p>
Own Id: OTP-9458</p>
</li>
</ul>
<h3><a name="id62949">1.4
Runtime_Tools 1.8.6</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Two new built-in trace pattern aliases have been added:
caller_trace (c) and caller_exception_trace (cx). See the
dbg:ltp/0 documentation for more info.</p>
<p>
Own Id: OTP-9458</p>
</li>
</ul>
<h3><a name="id62980">1.5
Runtime_Tools 1.8.5</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
When a big number of trace patterns are set by inviso the
Erlang VM could get unresponsive for several seconds.
This is now corrected.</p>
<p>
Own Id: OTP-9048 Aux Id: seq11480 </p>
</li>
</ul>
<h3><a name="id63010">1.6
Runtime_Tools 1.8.4.1</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
Minor corrections and removal of a temporary workaround.</p>
<p>
Own Id: OTP-8755 Aux Id: seq-11628, seq-11639 </p>
</li>
<li>
<p>
Small fix in inviso_autostart_server.</p>
<p>
Own Id: OTP-8783 Aux Id: seq11628 </p>
</li>
</ul>
<h3><a name="id58120">1.7
Runtime_Tools 1.8.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Miscellaneous updates.</p>
<p>
Own Id: OTP-8705</p>
</li>
</ul>
<h3><a name="id58149">1.8
Runtime_Tools 1.8.3</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Cross compilation improvements and other build system
improvements.</p>
<p>Most notable:</p> <ul>
<li> Lots of cross
compilation improvements. The old cross compilation
support was more or less non-existing as well as broken.
Please, note that the cross compilation support should
still be considered as experimental. Also note that old
cross compilation configurations cannot be used without
modifications. For more information on cross compiling
Erlang/OTP see the <span class="code">$ERL_TOP/INSTALL-CROSS.md</span> file.
</li>
<li> Support for staged install using <span class="bold_code"><a href="http://www.gnu.org/prep/standards/html_node/DESTDIR.html">DESTDIR</a></span>.
The old broken <span class="code">INSTALL_PREFIX</span> has also been fixed.
For more information see the <span class="code">$ERL_TOP/INSTALL.md</span>
file. </li>
<li> Documentation of the <span class="code">release</span>
target of the top <span class="code">Makefile</span>. For more information
see the <span class="code">$ERL_TOP/INSTALL.md</span> file. </li>
<li>
<span class="code">make install</span> now by default creates relative
symbolic links instead of absolute ones. For more
information see the <span class="code">$ERL_TOP/INSTALL.md</span> file.
</li>
<li> <span class="code">$ERL_TOP/configure --help=recursive</span>
now works and prints help for all applications with
<span class="code">configure</span> scripts. </li>
<li> Doing <span class="code">make
install</span>, or <span class="code">make release</span> directly after
<span class="code">make all</span> no longer triggers miscellaneous
rebuilds. </li>
<li> Existing bootstrap system is now
used when doing <span class="code">make install</span>, or <span class="code">make
release</span> without a preceding <span class="code">make all</span>.
</li>
<li> The <span class="code">crypto</span> and <span class="code">ssl</span>
applications use the same runtime library path when
dynamically linking against <span class="code">libssl.so</span> and
<span class="code">libcrypto.so</span>. The runtime library search path has
also been extended. </li>
<li> The <span class="code">configure</span>
scripts of <span class="code">erl_interface</span> and <span class="code">odbc</span> now
search for thread libraries and thread library quirks the
same way as <span class="code">erts</span> do. </li>
<li> The
<span class="code">configure</span> script of the <span class="code">odbc</span> application
now also looks for odbc libraries in <span class="code">lib64</span> and
<span class="code">lib/64</span> directories when building on a 64-bit
system. </li>
<li> The <span class="code">config.h.in</span> file in the
<span class="code">erl_interface</span> application is now automatically
generated in instead of statically updated which reduces
the risk of <span class="code">configure</span> tests without any effect.
</li>
</ul>
<p>(Thanks to Henrik Riomar for suggestions and
testing)</p>
<p>(Thanks to Winston Smith for the AVR32-Linux cross
configuration and testing)</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-8323</p>
</li>
<li>
<p>
Cleanups suggested by tidier and modernization of types
and specs.</p>
<p>
Own Id: OTP-8455</p>
</li>
</ul>
<h3><a name="id56501">1.9
Runtime_Tools 1.8.2</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The documentation is now built with open source tools
(xsltproc and fop) that exists on most platforms. One
visible change is that the frames are removed.</p>
<p>
Own Id: OTP-8201</p>
</li>
</ul>
<h3><a name="id56532">1.10
Runtime_Tools 1.8.1</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
<span class="code">Makefile.in</span> has been updated to use the LDFLAGS
environment variable (if set). (Thanks to Davide
Pesavento.)</p>
<p>
Own Id: OTP-8157</p>
</li>
</ul>
<h3><a name="id56566">1.11
Runtime_Tools 1.8</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
<span class="code">etop</span> would crash if the emulator's custom
allocators had been turned off (e.g. using the
<span class="code">+Meamin</span> option).</p>
<p>
Own Id: OTP-7519</p>
</li>
<li>
<p>The copyright notices have been updated.</p>
<p>
Own Id: OTP-7851</p>
</li>
<li>
<p>Now, dbg:p/2 accepts {X,Y,Z} process specification as
stated in the documentation. It also now accepts
"<X.Y.Z>" like from erlang:pid_to_list/1.</p>
<p>There is now a pre-saved match spec in dbg that saves
a lot of typing. Use dbg:ltp/0 to find out more...</p>
<p>
Own Id: OTP-7867</p>
</li>
</ul>
<h3><a name="id56633">1.12
Runtime_Tools 1.7.3</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Fixed a timestamp problem where some events could be
sent out of order. Minor fixes to presentation of
data.</p>
<p>
Own Id: OTP-7544 Aux Id: otp-7442 </p>
</li>
</ul>
<h3><a name="id56663">1.13
Runtime_Tools 1.7.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p><span class="code">etop</span> now collects process information faster
and more reliably than before (a race condition reported
by Igor Goryachev has been eliminated).</p>
<p>Trace messages could be lost when <span class="code">ttb:stop/0</span>
was called.</p>
<p>
Own Id: OTP-7164</p>
</li>
</ul>
<h3><a name="id56735">1.14
Runtime_Tools 1.7.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>The documentation has been updated so as to reflect
the last updates of the Erlang shell as well as the minor
modifications of the control sequence <span class="code">p</span> of the
<span class="code">io_lib</span> module.</p> <p>Superfluous empty lines have
been removed from code examples and from Erlang shell
examples.</p>
<p>
Own Id: OTP-6944 Aux Id: OTP-6554, OTP-6911 </p>
</li>
<li>
<p>Memory management improvements especially for the
runtime system with SMP support:</p> <ul> <li> The
runtime system with SMP support can now use multiple,
thread specific instances of most memory allocators. This
improves performance since it reduces lock contention in
the memory allocators. It may however increase memory
usage for some applications. The runtime system with SMP
support will by default enable this feature on most
allocators. The amount of instances used can be
configured. </li> <li> <span class="code">driver_alloc()</span>,
<span class="code">driver_realloc()</span>, and <span class="code">driver_free()</span> now use
their own erts specific memory allocator instead of the
default <span class="code">malloc()</span> implementation on the system.
</li> <li> The default configuration of some
allocators have been changed to fit applications that use
much memory better. </li> <li> Some new
<span class="code">erts_alloc</span> configuration parameters have been
added. </li> <li> <span class="code">erts_alloc_config</span> has been
modified to be able to create configurations suitable for
multiple instances of allocators. </li> <li> The
returned value from <span class="code">erlang:system_info({allocator,
Alloc})</span> has been changed. This since an allocator may
now run in multiple instances. </li> </ul> <p>If you
for some reason want the memory allocators to be
configured as before, you can pass the <span class="code">+Mea r11b</span>
command-line argument to <span class="code">erl</span>.</p> <p>For more
information see the <span class="code">erts_alloc(3)</span>, the
<span class="code">erts_alloc_config(3)</span>, and the <span class="code">erlang(3)</span>
documentation.</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-7100</p>
</li>
</ul>
<h3><a name="id56882">1.15
Runtime_Tools 1.7</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
<span class="code">dbg</span> could leave traced processes in a suspended
state if the tracer process was killed with exit reason
<span class="code">kill</span>.</p>
<p>
<span class="code">erlang:suspend_process/2</span> has been introduced which
accepts an option list as second argument. For more
information see the <span class="code">erlang(3)</span> documentation.</p>
<p>
Processes suspended via
<span class="code">erlang:suspend_process/[1,2]</span> will now be
automatically resumed if the process that called
<span class="code">erlang:suspend_process/[1,2]</span> terminates.</p>
<p>
Processes could previously be suspended by one process
and resumed by another unless someone was tracing the
suspendee. This is <strong>not</strong> possible anymore. The
process resuming a process <strong>has</strong> to be the one
that suspended it.</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-6946</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The undocumented and unsupported function
<span class="code">dbg:tracer/1</span> has been removed. The undocumented,
unsupported, and broken function <span class="code">dbg:i/1</span> has been
removed.</p>
<p>
Own Id: OTP-6939</p>
</li>
</ul>
<h3><a name="id64799">1.16
Runtime_Tools 1.6.8</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
In this release the following has been fixed and
enhanced: Autostart: It is now possible to configure
modules that shall be loaded by the autostart mechanism.
This because it is not certain that all application
systems make use of the OTP boot script to set up paths
to all Erlang modules. Runtime_tools/Inviso: A bug in the
fetch_log functionality has been fixed. Further a bug
that was (supposedly) fixed in a previous patch
concerning meta-tracer write_ti has been fixed (again) in
this patch. A bug in inviso_as_lib making remote
autostart config file updates fail has been fixed.
Inviso: inviso_tool has been given a flush API.</p>
<p>
Own Id: OTP-6918</p>
</li>
</ul>
<h3><a name="id64835">1.17
Runtime_Tools 1.6.7</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The following bugs/improvements have been done: Internal
interworking between inviso_rt and inviso_rt_meta. The
call function used by inviso_rt to call inviso_rt_meta is
now protected with a monitor. Inviso_rt_meta now includes
the timestamp of the incoming meta trace message when
calling the call-callback. (Makes it possible to add a
"better" timestamp to the ti-file.) Bug in inviso_tool
making it not remove trace patterns when terminating. Bug
in internal function h_start_session making inviso_tool
crash if there were no active nodes to start the session
on. The user-inviso_tool and inviso API-inviso control
component request/response gen_server protocols had
default time-out. Since many trace operations can be time
consuming, a longer time-out is necessary. Improved
overload protection. It is now possible to let the
overload protection renew itself (e.g after an exit from
an external overload protector). Inviso_rt_meta now fully
uses the exception_trace match spec action term. Run
Trace Case API (as in contrast to activate and deactivate
trace case APIs) in inviso_tool. Flush trace-port API
added to inviso. Get_session_data API added to
inviso_tool. Improved inviso_tool:stop making it possible
to name nodes which shall not have their trace patterns
removed when inviso_tool terminates. Bug in handling of
writing multiple ti-entries if returned from a
call/return_from call-back in inviso_rt_meta Process
trace flags are no longer explicitly removed by the
inviso_tool when it terminates. Not necessary.
Inviso_tool get_autostart_data adopted to standard
autostarter.</p>
<p>
*** INCOMPATIBILITY with Meta trace call-backs are called
with different arguments now. ***</p>
<p>
Own Id: OTP-6881</p>
</li>
</ul>
<h3><a name="id64887">1.18
Runtime_Tools 1.6.6</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>A bug in inviso_rt_meta caused an ETS table containing
information on initiated (init_tpm) functions to be lost
when suspending tracing. Further an enhancement to
inviso_rt has been introduced making it possible to
activate process trace flags based on globally registered
names. It is then not an error to activate a global name
on a node where the name does not reside. The process
count in the return value will simply be set to zero
(hence exactly one node in the NodeResult part of the
return value will indicate one matching process found). A
bug was found in fetch_log API. At the same time the
fetch_log functionality was enhanced to also offer flow
control making fetcher processes send chunks of
transferred file data at a slower pace.</p>
<p>Own Id: OTP-6703</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Minor Makefile changes.</p>
<p>Own Id: OTP-6689 Aux Id: OTP-6742 </p>
</li>
<li>
<p>An experimental tool called <span class="code">erts_alloc_config</span>
has been added. <span class="code">erts_alloc_config</span> is intended to
be used to aid creation of an <span class="code">erts_alloc</span>
configuration that is suitable for a limited number of
runtime scenarios. For more information see the
<span class="code">erts_alloc_config(3)</span> documentation.</p>
<p>Own Id: OTP-6700</p>
</li>
</ul>
<h3><a name="id64979">1.19
Runtime_Tools 1.6.5</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Misc improvements.</p>
<p>Own Id: OTP-6576</p>
</li>
</ul>
<h3><a name="id65011">1.20
Runtime_Tools 1.6.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>This application has been updated to eliminate warnings
by Dialyzer.</p>
<p>Own Id: OTP-6551</p>
</li>
</ul>
<h3><a name="id65043">1.21
Runtime_Tools 1.6.3</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>This ticket includes several improvements and bugfixes to
both runtime_tools and inviso. The overload mechanism can
now also react to incoming messages. This is useful if
an external overload watch-dog is used. Some improvements
of variable bindings has been done to the default
autostart mechanism - inviso_autostart_server. Autostart
"jobs" can now be done in parallel, allowing for some
jobs to hang waiting for some parts of the traced system
to become ready before proceeding. Previously when using
named meta-match-specs (tpm_ms) ending up with zero
match-specs still kept the meta trace pattern active.
This caused zero match-specs to be equal to unlimited
meta tracing on that particular function. If the internal
database becomes empty of meta match specs, meta trace
pattern is removed for that function. Standard public
loop data in the inviso runtime meta tracer process is
now extended to a 2-tuple. The functions ctp/1 and ctpl/1
are added making it possible to remove trace patterns for
a list of functions rather than one by one.
Inviso_rt_meta will now accept a list of binaries to be
output into the trace information file, in additions to a
single binary. Further it is also possible to make own
output to the trace information file using the write_ti/1
function. An error was discovered in inviso_rt making the
inviso_rt_meta remain rather than terminate if the
inviso_rt terminated due to "running alone" (not allowed
to run without a control component). A new tool,
inviso_tool, has been added to the inviso application.</p>
<p>Own Id: OTP-6426</p>
</li>
</ul>
<h3><a name="id65091">1.22
Runtime_Tools 1.6.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Several minor bugs and race conditions eliminated in the
runtime_tools and observer applications.</p>
<p>Own Id: OTP-6265</p>
</li>
</ul>
<h3><a name="id65124">1.23
Runtime_Tools 1.6.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>There are new BIFs <span class="code">erlang:spawn_monitor/1,3</span>,
and the new option <span class="code">monitor</span> for
<span class="code">spawn_opt/2,3,4,5</span>.</p>
<p>The <span class="code">observer_backend</span> module has been updated to
handle the new BIFs.</p>
<p>Own Id: OTP-6281</p>
</li>
</ul>
<h3><a name="id65176">1.24
Runtime_Tools 1.6</a></h3>
<p>Added the runtime part of the Inviso tracer, see the new Inviso
application for more information. This also meant adding an
application callback module and an application supervisor tree
for Runtime_Tools.</p>
<h3><a name="id65189">1.25
Runtime_Tools 1.5.1.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>The <span class="code">dbg</span> manual page has been updated with information
about how to avoid deadlock when tracing.</p>
<p>Own Id: OTP-5373 Aux Id: seq9729</p>
</li>
</ul>
<h3><a name="id65226">1.26
Runtime_Tools 1.5.1</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Linked in drivers in the Crypto, and Asn1 applications
are now compiled with the <span class="code">-D_THREAD_SAFE</span> and
<span class="code">-D_REENTRANT</span> switches on unix when the emulator has
thread support enabled.</p>
<p>Linked in drivers on MacOSX are not compiled with the
undocumented <span class="code">-lbundle1.o</span> switch anymore. Thanks to
Sean Hinde who sent us a patch.</p>
<p>Linked in driver in Crypto, and port programs in SSL, now
compiles on OSF1.</p>
<p>Minor <span class="code">Makefile</span> improvements in Runtime_Tools.</p>
<p>Own Id: OTP-5346</p>
</li>
</ul>
</div>
<div class="footer">
<hr>
<p>Copyright © 1999-2012 Ericsson AB. All Rights Reserved.</p>
</div>
</div>
</div></body>
</html>
distrib
>
Fedora
>
17
>
i386
>
media
>
updates
>
by-pkgid
>
675c8c8167236dfcf8d66da674f931e8
>
files
>
1242
