User's Guide
Reference Manual
Release Notes
PDF
Top

Observer
User's Guide
Version 0.9.8.2

Expand All
Contract All

Chapters

- Trace Tool Builder
  - Top of chapter
  - Introduction
  - Getting Started
  - Running the Trace Tool Builder against a remote node
  - Trace Information and the .ti File
  - Wrap Logs
  - Formatting
  - Automatically collect and format logs from all nodes
  - History and Configuration Files
  - Sequential Tracing
  - Example: Multipurpose trace tool
- Erlang Top
  - Top of chapter
  - Introduction
  - Output
  - Start
  - Configuration
  - Print to file
  - Stop
- Crashdump Viewer
  - Top of chapter
  - Introduction
  - Getting Started
  - Navigating
  - Help

# 3 Crashdump Viewer

### 3.1 Introduction

The Crashdump Viewer is an HTML based tool for browsing Erlang crashdumps. Crashdump Viewer runs under the WebTool application.

### 3.2 Getting Started

From an erlang node, start Crashdump Viewer by calling crashdump_viewer:start(). This will automatically start WebTool and display the web address where WebTool can be found. See the documentation for the WebTool application for further information about how to use WebTool.

Point your web browser to the address displayed, and you should now see the start page of WebTool. At the top of the page, you will see a link to "CrashDumpViewer". Click this link to get to the start page for Crashdump Viewer. (Note that if webtool is on localhost, you must configure your web browser to have direct connection to the internet, or you must set no proxy for localhost.)

You can also start WebTool, Crashdump Viewer and a browser in one go by running the start_webtool script found in the priv directory of the WebTool application, e.g.
>start_webtool crashdump_viewer

From the start page of Crashdump Viewer, push the "Load Crashdump" button to load a crashdump into the tool. Then enter the filename of the crashdump in the entry field and push the "Ok" button.

Crashdumps generated by OTP R9C and later are loaded directly into the Crashdump Viewer, while dumps from earlier releases first are translated by the Crashdump Translater. The Crashdump Translater creates a new file with the same name as the original crashdump, but with the extension .translated. If there is no write access to the directory of the original file, you will be asked to enter a new path and filename for the translated file.

### 3.3 Navigating

The lefthand frame contains a menu. Menu folders can be expanded and collapsed by clicking the folder picture. When a menu item is clicked, the item information is shown in the big information frame.

The filename frame above the information frame shows the full name of the currently viewed Erlang crashdump.

To load a new crashdump, click the "Load New Crashdump" button in the menu frame.

The various information shown in the information frame will contain links to process identifiers (PIDs) and port identifiers. Clicking one of these links will take you to the detailed information page for the process or port in question. Use the "Back" button in your browser to get back to the startingpoint. If the process or port resided on a remote node, there will be no information available. Clicking the link will then take you to the information about the remote node.

### 3.4 Help

Further help on how to use the Crashdump Viewer tool can be found in the tool's menu under 'Documentation':

'Crashdump Viewer help' is a short document describing each information page and any additional information that might occur, compared to the raw dump described in 'How to interpret Erlang crashdumps'.

'How to interpret Erlang crashdumps' is a document from the Erlang runtime system describing details in the raw crashdumps. Here you will also find information about each single field in the different information pages. This document can also be found directly in the OTP online documentation, via the Erlang runtime system user's guide.