<!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 -- SASL 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="users_guide.html">User's Guide</a><br><a href="index.html">Reference Manual</a><br><a href="release_notes.html">Release Notes</a><br><a href="../pdf/sasl-2.2.1.pdf">PDF</a><br><a href="../../../../doc/index.html">Top</a></small><p><strong>System Application Support Libraries (SASL)</strong><br><strong>Release Notes</strong><br><small>Version 2.2.1</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="SASL Release Notes" expanded="true">SASL Release Notes<ul>
<li><a href="notes.html">
Top of chapter
</a></li>
<li title="SASL 2.2.1"><a href="notes.html#id59998">SASL 2.2.1</a></li>
<li title="SASL 2.2"><a href="notes.html#id61784">SASL 2.2</a></li>
<li title="SASL 2.1.10"><a href="notes.html#id65329">SASL 2.1.10</a></li>
<li title="SASL 2.1.9.4"><a href="notes.html#id56499">SASL 2.1.9.4</a></li>
<li title="SASL 2.1.9.3"><a href="notes.html#id66144">SASL 2.1.9.3</a></li>
<li title="SASL 2.1.9.2"><a href="notes.html#id61941">SASL 2.1.9.2</a></li>
<li title="SASL 2.1.9.1"><a href="notes.html#id61980">SASL 2.1.9.1</a></li>
<li title="SASL 2.1.9"><a href="notes.html#id62018">SASL 2.1.9</a></li>
<li title="SASL 2.1.8"><a href="notes.html#id62102">SASL 2.1.8</a></li>
<li title="SASL 2.1.7"><a href="notes.html#id60604">SASL 2.1.7</a></li>
<li title="SASL 2.1.6"><a href="notes.html#id60635">SASL 2.1.6</a></li>
<li title="SASL 2.1.5.4"><a href="notes.html#id60699">SASL 2.1.5.4</a></li>
<li title="SASL 2.1.5.3"><a href="notes.html#id60729">SASL 2.1.5.3</a></li>
<li title="SASL 2.1.5.2"><a href="notes.html#id60164">SASL 2.1.5.2</a></li>
<li title="SASL 2.1.5.1"><a href="notes.html#id60195">SASL 2.1.5.1</a></li>
<li title="SASL 2.1.5"><a href="notes.html#id60239">SASL 2.1.5</a></li>
<li title="SASL 2.1.4"><a href="notes.html#id60287">SASL 2.1.4</a></li>
<li title="SASL 2.1.3"><a href="notes.html#id59427">SASL 2.1.3</a></li>
<li title="SASL 2.1.2"><a href="notes.html#id59471">SASL 2.1.2</a></li>
<li title="SASL 2.1.1"><a href="notes.html#id59507">SASL 2.1.1</a></li>
<li title="SASL 2.1"><a href="notes.html#id59578">SASL 2.1</a></li>
<li title="SASL 2.0.1"><a href="notes.html#id59637">SASL 2.0.1</a></li>
</ul>
</li></ul>
</div></div>
<div id="content">
<div class="innertube">
<h1>1 SASL Release Notes</h1>
<p>This document describes the changes made to the SASL application.</p>
<h3><a name="id59998">1.1
SASL 2.2.1</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
If sys.config existed, but was not readable or parseable,
this would not be detected until after the upgrade and at
the next node restart. The possibility for this to happen
is now reduced by adding a check to systools:make_tar
which fails the creation of the tar file if sys.config or
relup does not have reasonable contents. Note that there
are no detailed checks, only parsing and erlang term
format check.</p>
<p>
Own Id: OTP-9539</p>
</li>
<li>
<p>
systools:make_script would allow {kernel,Vsn,load} in the
.rel file, causing a .boot file which only loaded kernel
and did not start it. This has been corrected. Only start
type 'permanent', which is the default, is now allowed
for kernel and stdlib.</p>
<p>
Own Id: OTP-9652</p>
</li>
<li>
<p>
release_handler:remove_release/1 now handles symlinked
files properly</p>
<p>
Own Id: OTP-9864</p>
</li>
<li>
<p>
If stdlib was stated with a start type different from
<span class="code">permanent</span> in a .rel file, systools would
incorrectly say that sasl had faulty start type. This has
been corrected.</p>
<p>
Own Id: OTP-9888</p>
</li>
<li>
<p>
Sasl documentation earlier said that the InclApps
parameters in a .rel file defaults to the empty list.
This is not correct. It defaults to the same value as
specified in the .app file. This has been corrected.</p>
<p>
Own Id: OTP-9980</p>
</li>
<li>
<p>
Applications that are listed in
<span class="code">{applications,Apps}</span> in the .app file were not
sorted correctly by <span class="code">systools:make_script/1,2</span>. They
got the reverse order of how they were listed in the .app
file. This is corrected so they are now sorted
(internally between each other) in the same order as they
are listed in the .rel file (i.e. the order they are
listed in the .app file does no longer matter).</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-9984</p>
</li>
<li>
<p>
Documentation of .appup files now also states that
<span class="code">UpFromVsn</span> and <span class="code">DownToVsn</span> can be specified as
regular expressions in order to avoid duplicated upgrade
instructions.</p>
<p>
Own Id: OTP-10001</p>
</li>
<li>
<p>
Reltool would sometimes generate a .app file containing
<span class="code">{start_phases,undefined}</span>, which would cause an
exception in systools at parse time. This has been
corrected so reltool now omits the <span class="code">start_phases</span>
entry if the value is <span class="code">undefined</span>. (Thanks to Juan
Jose Comellas)</p>
<p>
In order to align with reltool, sasl will also omit
<span class="code">start_phases</span> entries with value <span class="code">undefined</span>
in .script files.</p>
<p>
Own Id: OTP-10003</p>
</li>
</ul>
<h3><a name="id61784">1.2
SASL 2.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
Fix the mechanism for upgrading emulator.</p>
<p>
The appup files for kernel, stdlib and sasl do now
recognize two major releases back and include a
'restart_new_emulator' instruction. </p>
<p>
Appup files can include regular expressions for matching
earlier releases.</p>
<p>
The mechanism for upgrading the emulator is changed so
'restart_new_emulator' will be the first instruction
executed. The rest of the upgrade instruction will be
executed after the emulator restart.</p>
<p>
A new upgrade instruction 'restart_emulator' is added for
the case where the emulator shall be restarted after all
other upgrade instructions.</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-9438</p>
</li>
<li>
<p>
Add release_handler:which_releases/1</p>
<p>
This is an extension to which_releases that allows a user
to specify the status of the releases they wish to be
returned. For instance it allows for quickly determining
which release is 'permanent' without the need of parsing
the entire release list. (Thanks to Joe Williams)</p>
<p>
Own Id: OTP-9717</p>
</li>
<li>
<p>
Add copy of rel file in releases/Vsn in release tar file</p>
<p>
systool:make_tar stores the rel file in the releases
directory. When unpacking with
release_handler:unpack_release, the file is automatically
moved to releases/Vsn/. If, however, the tar file is
unpacked manually, the rel file might not be moved, and
the next release unpacked might overwrite the rel file.
To overcome this, systools:make_tar now stores a copy of
the rel file in releases/Vsn/ directly and it is not
longer necessary to move the file after unpacking.</p>
<p>
The reason for keeping the file in the releases directory
also is that is needs to be extracted separately before
the release version (Vsn) is known.</p>
<p>
Own Id: OTP-9746</p>
</li>
</ul>
<h3><a name="id65329">1.3
SASL 2.1.10</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
The release_handler functionality on windows services was
broken. This has been corrected.</p>
<p>
Own Id: OTP-9306</p>
</li>
<li>
<p>
If a new version of an application did not include any
erlang module changes, the code path of the application
was not updated by the release_handler unless a
'load_object_code' instruction was added for the
application. This would be a problem if e.g. only some
files in the priv dir were changed since calls to
code:lib_dir or code:priv_dir would then point to the old
location of the application. This has been corrected -
now code:replace_path/2 will be called for all
applications that are changed (i.e. when the
application's vsn is changed in the .rel file).</p>
<p>
Own Id: OTP-9402</p>
</li>
<li>
<p>
The appup instruction 'delete_module' would cause a crash
during upgrade if the module to be deleted was not
loaded. This has been corrected.</p>
<p>
Own Id: OTP-9417</p>
</li>
<li>
<p>
If a path was given as ONLY 'ebin' and not for example
'./ebin', then systools:make_tar would fail with a
<span class="code">function_clause</span> exception in filename:join/1. This
has been corrected. (Thanks to Nikola Skoric for
reporting).</p>
<p>
Own Id: OTP-9507</p>
</li>
<li>
<p>
Implement or fix -Werror option</p>
<p>
If -Werror is enabled and there are warnings no output
file is written. Also make sure that error/warning
reporting is consistent. (Thanks to Tuncer Ayaz)</p>
<p>
Own Id: OTP-9536</p>
</li>
<li>
<p>
Improved error information for timeouts during
release_handler:install_release.</p>
<p>
This patch addresses two cases where a timeout will occur
during upgrade. 1) if a supervisor is suspended (call to
get children from supervisor will hang) 2) if the child
spec for a supervisor incorrectly states that it is a
worker with a dynamic set of modules (call to get modules
from gen_event will hang)</p>
<p>
An error report will now be printed, and the return value
of release_handler:install_release will indicate what
happened. (Thanks to joe williams)</p>
<p>
Own Id: OTP-9546</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
<span class="code">release_handler:install_release</span> could be very slow
when there are many processes in the system. Some
optimization work has been done both in erts and in the
release handler in order to improve this. </p>
<p>
A new option, <span class="code">purge</span>, is added to
<span class="code">release_handler:check_install_release</span> which can be
called first in order to speed up the execution of
<span class="code">release_handler:install_release</span>.</p>
<p>
Own Id: OTP-9395</p>
</li>
</ul>
<h3><a name="id56499">1.4
SASL 2.1.9.4</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>
Remove traces of release_handler reading from filesystem
when it has Masters list</p>
<p>
There are a couple of places in release_handler and
release_handler_1 that assumed it has a disk to read
from, which in the case of an erl_prim_loader Loader
other than efile is not necessarily true</p>
<p>
Add check_paths/2 to do the equivalent of check_path/1
for when there is a Masters list</p>
<p>
Change get_vsn to no longer get sent File paths but
instead use the Bin since beam_lib:version being sent a
file path causes it to read the local file system</p>
<p>
Add get_current_vsn/1 as an equivalent to
beam_lib:version(code:which(Mod)), but using
erl_prim_loader:get_file instead of reading from local
file system</p>
<p>
(Thanks to Steven Gravell)</p>
<p>
Own Id: OTP-9142</p>
</li>
<li>
<p>
rb:stop did sometimes return {error,running}. This came
from supervisor:delete_child and happened when the
rb_server has not yet terminated when this function was
called. Instead of having a separate gen_server call to
rb_server for stopping the process,
supervisor:terminate_child is now called. This is a
synchronous function - i.e. it waits for the process to
actually terminate before it returns.</p>
<p>
A file descriptor leak in rb:scan_files is corrected. The
index file was never closed after reading.</p>
<p>
A mismatch in the behavior of rb:filter, when filter
included 'no', is corrected. Such filters will now return
*all* non-matching reports, not only the 'proplist'
reports.</p>
<p>
Own Id: OTP-9149</p>
</li>
<li>
<p>
Start and end date for rb:filter/2 was specified as
{{Y-M-D},...} in the help text instead of {{Y,M,D},...}.
This has been corrected.</p>
<p>
Own Id: OTP-9166</p>
</li>
<li>
<p>
If some, but not all, of the sasl environment variables
related to the log_mf_h error handler were missing sasl
would successfully start but silently skip starting
log_mf_h. This is corrected so sasl startup will now fail
if one or two of the three variables are given. If none
of the variables are given, sasl will start as before
without starting log_mf_h.</p>
<p>
Own Id: OTP-9185</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Change default behaviour to not check src code when
creating release</p>
<p>
Add new option <span class="code">src_tests</span> to systools:make_script
and systools:make_tar. The old option
<span class="code">no_module_tests</span> is now ignored as this is the
default behaviour.</p>
<p>
*** POTENTIAL INCOMPATIBILITY ***</p>
<p>
Own Id: OTP-9146 Aux Id: seq11803 </p>
</li>
</ul>
<h3><a name="id66144">1.5
SASL 2.1.9.3</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Honor start type in .rel files when building relup files</p>
<p>
Previously, relup file always included an
application:start(Application, permanent) apply
instruction for every application that appear in the
UpTo/DowFrom release file, whatever their start type in
the release file.</p>
<p>
The new implementation fixes this bug by honoring the
start type according to the rel(5) format. If the start
type is none, no apply line is included in the relup. If
the start type is load, the relup includes instruction to
only load the application. Otherwise, the relup includes
an instruction to start the application to the according
type.</p>
<p>
The fix is implemented by adding a new parameter to the
add_application high level appup instruction. This new
parameter is documented in appup(5).</p>
<p>
Own Id: OTP-9097</p>
</li>
</ul>
<h3><a name="id61941">1.6
SASL 2.1.9.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>In R13B04 sys:get_status was modified to invoke
format_status/2 in the callback module if the module
exports that function. This resulted in a change to the
term returned from calling sys:get_status on the
supervisor module, since supervisor is a gen_server and
gen_server exports format_status. The sasl
release_handler_1 module had a dependency on the
pre-R13B04 term returned by sys:get_status when invoked
on a supervisor, so the R13B04 change broke that
dependency.</p>
<p>This problem has been fixed by change
release_handler_1 to handle both the pre-R13B04 and
R13B04 terms that sys:get_status can return from a
supervisor.</p>
<p>
Own Id: OTP-8619 Aux Id: seq11570 </p>
</li>
</ul>
<h3><a name="id61980">1.7
SASL 2.1.9.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Use an infinity timeout in all calls to
<span class="code">gen_server:call()</span> in the <span class="code">sasl</span>
application.</p>
<p>
Own Id: OTP-8506 Aux Id: seq11509 </p>
</li>
</ul>
<h3><a name="id62018">1.8
SASL 2.1.9</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The <span class="code">re:grep/1</span> function now uses the '<span class="code">re</span>'
module instead of the deprecated '<span class="code">regexp</span>' module.
There are new functions <span class="code">rb:filter/1</span> and
<span class="code">rb:filter/2</span> for easier filtering of reports.
(Thanks to Alvaro Videla.)</p>
<p>
Own Id: OTP-8443</p>
</li>
<li>
<p>
There is new function <span class="code">sasl_report:format_report/3</span>
that works like the existing
<span class="code">sasl_report:write_report/3</span> function except that it
returns a formatted string. Note that there is currently
no documentation for the <span class="code">sasl_report</span> module.
(Thanks to Jay Nelson.)</p>
<p>
Own Id: OTP-8445</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="id62102">1.9
SASL 2.1.8</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="id60604">1.10
SASL 2.1.7</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
The Windows utility Erlsrv, run in interactive mode now
accepts options for registering internal service name and
description field of Windows registry database.</p>
<p>
Own Id: OTP-8132</p>
</li>
</ul>
<h3><a name="id60635">1.11
SASL 2.1.6</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>When using the SASL application configuration
parameter <span class="code">masters</span> the error tuple
<span class="code">{error,{no_such_file,{Master,FileName}}}</span> was
sometimes returned even though the file <span class="code">FileName</span>
existed.</p>
<p>
Own Id: OTP-7667</p>
</li>
</ul>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Missing preloaded modules added</p>
<p>
Own Id: OTP-7820</p>
</li>
</ul>
<h3><a name="id60699">1.12
SASL 2.1.5.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
A Dialyzer warning was eliminated</p>
<p>
Own Id: OTP-7635</p>
</li>
</ul>
<h3><a name="id60729">1.13
SASL 2.1.5.3</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Minor changes.</p>
<p>
Own Id: OTP-7388</p>
</li>
</ul>
<h3><a name="id60164">1.14
SASL 2.1.5.2</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>
Minor updates.</p>
<p>
Own Id: OTP-6998</p>
</li>
</ul>
<h3><a name="id60195">1.15
SASL 2.1.5.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Minor Makefile changes.</p>
<p>Own Id: OTP-6689</p>
</li>
<li>
<p>Obsolete guard tests (such as list()) have been replaced
with the modern guard tests (such as is_list()).</p>
<p>Own Id: OTP-6725</p>
</li>
</ul>
<h3><a name="id60239">1.16
SASL 2.1.5</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Removed some dead code from <span class="code">erlsrv:get_service/2</span>,
<span class="code">release_handler:do_write_file/2</span>,
<span class="code">systools_relup:foreach_baserel_up/7</span> and
<span class="code">systools_relup:foreach_baserel_dn/7</span>.</p>
<p>Own Id: OTP-6499</p>
</li>
</ul>
<h3><a name="id60287">1.17
SASL 2.1.4</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Added an option <span class="code">{outdir,Dir}</span> to the functions in
<span class="code">systools</span>, making it possible to specify in which
directory a boot script, relup file or release package
file should be placed.</p>
<p>Also, when using <span class="code">systools:make_tar/2</span> to create a
release package file, the boot script, relup file and
<span class="code">sys.config</span> are now searched for also in the current
working directory and any directory specified by
the <span class="code">path</span> option, not only in the directory of
the <span class="code">.rel</span> file.</p>
<p>As part of the work some minor bugs have been corrected:</p>
<ul>
<li>
<p><span class="code">systools:make_script/1,2</span> now returns
<span class="code">error</span> if the <span class="code">.script</span> and/or <span class="code">.boot</span>
file could not be opened for writing, not <span class="code">ok</span>.</p>
</li>
<li>
<p><span class="code">systools:make_tar/1,2</span> can now handle a
<span class="code">RelName</span> argument which includes a path.
Previously this would cause the <span class="code">.rel</span> file to end
up in the wrong directory in the resulting tar file.</p>
</li>
<li>
<p>A documentation error for <span class="code">systools:make_tar/1,2</span>:
The <span class="code">.rel</span> file is placed in the <span class="code">releases</span>
directory in the tar file, not <span class="code">releases/RelVsn</span>.</p>
</li>
</ul>
<p>Own Id: OTP-6226</p>
</li>
</ul>
<h3><a name="id59427">1.18
SASL 2.1.3</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p><span class="code">release_handler:upgrade_app/2</span> and
<span class="code">release_handler:downgrade_app/2,3</span> -- used for
testing application upgrade and downgrade according to
the <span class="code">.appup</span> file -- now update application
configuration parameters correctly. (Thanks to Serge
Aleynikov)</p>
<p>Own Id: OTP-6162</p>
</li>
</ul>
<h3><a name="id59471">1.19
SASL 2.1.2</a></h3>
<h4>Fixed Bugs and Malfunctions</h4>
<ul>
<li>
<p>Fixed some minor bugs in <span class="code">release_handler</span> found by
Dialyzer.</p>
<p>Own Id: OTP-6039</p>
</li>
</ul>
<h3><a name="id59507">1.20
SASL 2.1.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>Added a number of functions to <span class="code">release_handler</span> which
makes it possible to test upgrade and downgrade of
applications according to an <span class="code">.appup</span> file "on the
fly": <br>
- <span class="code">upgrade_app/2</span> <br>
- <span class="code">upgrade_script/2</span> <br>
- <span class="code">downgrade_app/2,3</span> <br>
- <span class="code">downgrade_script/3</span> <br>
- <span class="code">eval_appup_script/4</span></p>
<p>Own Id: OTP-5858</p>
</li>
</ul>
<h3><a name="id59578">1.21
SASL 2.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>A new option <span class="code">{update_paths,Bool}</span> has been added
for <span class="code">release_handler:install_release/2</span>. It
indicates if all application code paths should be updated
(<span class="code">Bool==true</span>), or if only code paths for modified
applications should be updated (<span class="code">Bool==false</span>,
default).</p>
<p><span class="code">release_handler:set_unpacked/2</span> now returns an
error tuple if a specified application directory does not
exist.</p>
<p>*** POTENTIAL INCOMPATIBILITY ***</p>
<p>Own Id: OTP-5761</p>
</li>
</ul>
<h3><a name="id59637">1.22
SASL 2.0.1</a></h3>
<h4>Improvements and New Features</h4>
<ul>
<li>
<p>A bug that made it impossible to call <span class="code">rb:show(N)</span>
(<span class="code">N</span> being an integer) twice without getting an error
has been fixed.</p>
<p>Own Id: OTP-5287</p>
</li>
</ul>
</div>
<div class="footer">
<hr>
<p>Copyright © 1997-2012 Ericsson AB. All Rights Reserved.</p>
</div>
</div>
</div></body>
</html>
