Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Erlang C C++ Makefile Java HTML Other

Merge tag 'erl_1219' into maint

erts: Patch 1219

   OTP-10602  Create an erl_crash.dump if no heart exists and no ERL_CRASH_DUMP_SECONDS
              is set (behaviour changed). Don't create an erl_crash.dump
              if heart do exists and no ERL_CRASH_DUMP_SECONDS is set
              (behaviour not changed). This changes the behaviour back
              to the R15B02 default considering if a beam was running
              with no heart.
latest commit 1cbd897c43
@psyeugenic psyeugenic authored
Failed to load latest commit information.
erts Merge tag 'erl_1219' into maint
make [safs] Add pdfname to the html target for the users guide
.gitignore Ignore common_test bootstrap
EPLICENCE Clean up Install Erlang on OSX
README.bootstrap Update README's for dtrace and systemtap
aclocal.m4 OTP-8323 Cross compilation improvements and other build system
otp_build Update copyright years
prebuild.skip OTP-8323 Cross compilation improvements and other build system


Erlang is a programming language used to build massively scalable soft real-time systems with requirements on high availability. Some of its uses are in telecom, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance.

OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. It includes its own distributed database, applications to interface towards other languages, debugging and release handling tools.

More information can be found at

Building and Installing

Information on building and installing Erlang/OTP can be found in the document.

Contributing to Erlang/OTP

Here are the instructions for submitting patches.

In short:

  • We prefer to receive proposed updates via email on the erlang-patches mailing list rather than through a pull request. Pull requests are not practical because we have a strict policy never to merge any untested changes to the development branch (the only exception being obviously correct changes, such as corrections of typos).

  • We merge all proposed updates to the pu (proposed updates) branch, typically within one working day.

  • At least once a day, the contents of the pu branch will be built on several platforms (Linux, Solaris, Mac OS X, Windows, and so on) and automatic test suites will be run. We will email you if any problems are found.

  • If a proposed change builds and passes the tests, it will be reviewed by one or more members of the Erlang/OTP team at Ericsson. The reviewer may suggest improvements that are needed before the change can be accepted and merged.

  • Once or twice a week, a status email called "What's cooking in Erlang/OTP" will be sent to the erlang-patches mailing list.

Copyright and License


Copyright Ericsson AB 2010-2012. All Rights Reserved.

The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at

Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.


Something went wrong with that request. Please try again.