Bug 1291856 - When aborting due to large distribution, Erlang does not produce a crash dump
Summary: When aborting due to large distribution, Erlang does not produce a crash dump
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: erlang
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: ---
: 6.0 (Juno)
Assignee: John Eckersberg
QA Contact: Udi Kalifon
URL:
Whiteboard:
Depends On: 1291822
Blocks: 1291855
TreeView+ depends on / blocked
 
Reported: 2015-12-15 17:51 UTC by John Eckersberg
Modified: 2023-02-22 23:02 UTC (History)
8 users (show)

Fixed In Version: erlang-R16B-03.7min.3.el7ost
Doc Type: Bug Fix
Doc Text:
Clone Of: 1291822
Environment:
Last Closed: 2016-06-08 12:09:56 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1211 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform 6 Bug Fix and Enhancement Advisory 2016-06-08 16:08:56 UTC

Description John Eckersberg 2015-12-15 17:51:40 UTC 
+++ This bug was initially created as a clone of Bug #1291822 +++

Erlang aborts in dist_port_command with ERTS_ABORT_EXIT:

    if (size > (Uint) INT_MAX)
	erl_exit(ERTS_ABORT_EXIT,
		 "Absurdly large distribution output data buffer "
		 "(%beu bytes) passed.\n",
		 size);

However, ERTS_ABORT_EXIT inhibits erlang crash dump generation.  It would be better to exit with ERTS_DUMP_EXIT so a crash dump is generated, in order to help debug crashes from large messages.
Comment 3 Udi Kalifon 2016-05-30 08:57:03 UTC 
Verified in Juno 2016-05-04 with erlang-R16B-03.7min.3.el7ost.x86_64, using the explosivo.sh script from bug #1291822.
Comment 5 errata-xmlrpc 2016-06-08 12:09:56 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1211
Note You need to log in before you can comment on or make changes to this bug.