The following bugs in ttb have been corrected:

ttb:tracer/2 would earlier crash when trying to set up tracing for a diskless node to wrap files, i.e. when option {file,{local,{wrap,Filename,Size,Count}}} was used. ttb:stop([fetch]) would sometimes silently fail if multiple nodes with different current working directories were traced. ttb:stop([fetch]) would crash if the tracer was started with option {file,{local,Filename}} A deadlock would sometimes occur due to an information printout from the ttb_control process when ttb was stopped.

Own Id: OTP-9431

The file trace port to which the IP trace client relays all traces from diskless nodes was not flushed and closed properly on ttb:stop. This has been corrected.

Own Id: OTP-9665

A new GUI for Observer. Integrating pman, etop, appmon and tv into observer with tracing facilities.

Own Id: OTP-4779

The following new features are added to ttb:

A one-command trace setup is added, ttb:start_trace/4. The following new options are added to ttb:tracer/2: shell - Show trace messages on the console in real time timer - Time constrained tracing overload - Overload protection flush - Flush file trace port buffers with given frequency resume - Automatically resume tracing after node restart A new shortcut is added for common tracer settings similar to using the dbg module directly, ttb:tracer(shell | dbg). Some shortcuts are added for commonly used match specifications in ttb:tp and ttb:tpl. The Options argument to functions ttb:tracer, ttb:write_config, ttb:stop and ttb:format may now be one single option instead of a list. The history buffer of the last trace is now always automatically dumped to the file ttb_last_config when ttb:stop is called. The following new options are added to ttb:stop/1: fetch_dir - Specify where to store fetched logs {format,FormatOpts} - Specify options to use when formatting the fetched logs return_fetch_dir - Indicate that the return value from ttb:stop/1 should include the name of the directory where the fetched logs are stored The option disable_sort is added to ttb:format/2. When this option is used, trace messages from different logs are not merged according to timestamps, but just appended one log after the other.

Own Id: OTP-9403

The following non backwards compatible changes are done in ttb:

When setting up trace with ttb, the 'timestamp' trace flag will now always be set. The 'fetch' option to ttb:stop/1 is removed since it is now default behavior that trace logs are fetched when stopping ttb. Fetching can be disabled with the 'nofetch' option to ttb:stop/1. The name of the upload directory is changed from ttb_upload-Timestamp to ttb_upload_FileName-Timestamp. To format the output using 'et', you now need to provide the option {handler,ttb:get_et_handler()} instead of {handler,et}. When formatting a trace log, the handler state was earlier reset after each trace file, this is now changed so the handler state is passed not only from one trace message to the next in the same file, but also from one file to the next.

*** POTENTIAL INCOMPATIBILITY ***

Own Id: OTP-9430

Do not install *.bat files on non-win32 machines (Thanks to Hans Ulrich Niedermann)

Own Id: OTP-9515

The time needed for loading a crashump into the crashdump viewer would earlier grow exponentially with the size of the crashdump file. Reading a file of 20M would take a couple of minutes, and for a dump of 250M it would take between 1 and 2 hours. This has been solved.

Earlier, all processes, timers, funs or ets-tables would be loaded into the memory of the crashdump viewer node before sending it on to the web server. This has been changed and the pages are now sent to the web server in chunks.

A security function in newer web browsers prevents a full file path to be sent from an HTML file input field, i.e. the field needed to implement the "Browse" button when loading a file into the crashdump viewer. To overcome this, the file input field is no longer used. Instead a normal text input field is used, and the user needs to manually insert the complete file path. For convenience, a shell script and a batch file are added to the observer application. These can be used to start the crashdump_viewer and a browser and load a file - with the file name given from the command line. The shell script and batch file are called cdv and cdv.bat respectively, and can be found in the priv dir of the observer application.

Own Id: OTP-9051 Aux Id: seq11789

The multitrace.erl installation example file is now installed in the examples directory. (Thanks to Peter Lemenkov.)

Own Id: OTP-8857

The test suite has been updated for R14A.

Own Id: OTP-8708

Misc updates

Own Id: OTP-8456

Major improvements of the Erlang distribution for Erlang runtime systems with SMP support. Previously distribution port locks were heavily contended, and all encoding and decoding for a specific distribution channel had to be done in sequence. Lock contention due to the distribution is now negligible and both encoding and decoding of Erlang messages can be done in parallel.

The old atom cache protocol used by the Erlang distribution has been dropped since it effectively prevented all parallel encoding and decoding of messages passed over the same distribution channel.

A new atom cache protocol has been introduced which isolates atom cache accesses and makes parallel encoding and decoding of messages passed over the same distribution channel possible. The new atom cache protocol also use an atom cache size 8 times larger than before. The new atom cache protocol is documented in the ERTS users guide.

Erlang messages received via the distribution are now decoded by the receiving Erlang processes without holding any distribution channel specific locks. Erlang messages and signals sent over the distribution are as before encoded by the sending Erlang process, but now without holding any distribution channel specific locks during the encoding. That is, both encoding and decoding can be and are done in parallel regardless of distribution channel used.

The part that cannot be parallelized is the atom cache updates. Atom cache updates are therefore now scheduled on the distribution port. Since it is only one entity per distribution channel doing this work there is no lock contention due to the atom cache updates.

The new runtime system does not understand the old atom cache protocol. New and old runtime systems can however still communicate, but no atom cache will be used.

Own Id: OTP-7774

etop would crash if the emulator's custom allocators had been turned off (e.g. using the +Meamin option).

Own Id: OTP-7519

The copyright notices have been updated.

Own Id: OTP-7851

Minor Makefile changes.

Own Id: OTP-6689

Obsolete guard tests (such as list()) have been replaced with the modern guard tests (such as is_list()).

Own Id: OTP-6725

This application has been updated to eliminate warnings by Dialyzer.

Own Id: OTP-6551

Several minor bugs and race conditions eliminated in the runtime_tools and observer applications.

Own Id: OTP-6265

Crash dump with large integers could crash the crashdump_viewer.

Own Id: OTP-6301

Fixed a bug in etop which made the Load and Memory information in the header incorrect -- for example the value shown for binary (memory allocated for binaries) was actually the number of currently running processes. (Thanks to Rikard Johansson.)

Own Id: OTP-6075

The Observer application has been recompiled because of a compiler bug.

Own Id: OTP-5700

crashdump_viewer is faster when showing message, dictionary, and stack dump for large processes.

Own Id: OTP-5408