| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
erts/emulator/sys/vxworks/sys.c
erts/vsn.mk
lib/ssl/src/ssl_connection.erl
lib/ssl/test/ssl_basic_SUITE.erl
|
|
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.
|
|
|
|
* bjorn/remove-tuple-funs/OTP-10170:
erl_expand_records: Remove stale support for literal tuple funs
Teach is_function/2 that tuples are not funs
|
|
* sverk/bs_construct_SUITE-outofmem:
erts: Limit memory usage of bs_construct_SUITE:huge_binary
|
|
* ta/docsmaster:
Fix various doc typos for R16
Fix various typos in HOWTO/ for R16
Fix various comment typos for R16
OTP-10611
|
|
|
|
|
|
Conflicts:
erts/emulator/beam/io.c
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* 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.
The motivation is that we want a fast heart to fast restart erlang if
it crashes but to be able to get non-truncated erl_crash.dumps via
setting ERL_CRASH_DUMP_SECONDS if we so desire.
|
|
|
|
depending on the amount of free memory on the host
|
|
|
|
* sverk/crypto-unloading:
crypto: Link crypto_callback statically
crypto: Add debug print macros
crypto: Enable runtime upgrade of crypto
crypto: Make unloading of crypto safer
OTP-10596
|
|
* Measurements suggests that memcpy is a bit faster for small tuples
and ~50% faster for large tuples. (Linux kernel-3.2.0).
|
|
* ?line is not needed anymore and should be removed when
a test_SUITE is changed.
|
|
|
|
Erlang specification 4.7.3 defines max tuple size to 65535 elements
It is now defined to 16777215 elements (24 bits)
|
|
* egil/darwin-fixes:
erl_interface: Avoid redefinition of ALIGNBYTES
erts: Fix '#ifdef' for unused static functions
erts: Remove forgotten vxworks includes
hipe: Cast offsetof to int in hipe_arch_print_pcb
|
|
Also made check for DLL version against redistributables
instead of towards installed system, as some builds
required redistributables everytime (installed dll on build
machine had higher version than the redist)...
|
|
The R15B03 release
|
|
|
|
|
|
Conflicts:
erts/doc/src/erlang.xml
|
|
* pan/process_info_spec_doc/r15/OTP-10584:
Correct doc of process_info(Pid,links)
OTP-10584
|
|
* pan/bs_append_crash:
Teach erts_bs_append not to dump core
OTP-10590
|
|
|
|
|
|
|
|
* egil/fix-crash_dump-lc-assert:
erts: Suppress lock assertion when dumping a crash
|
|
|
|
When erts_bs_append() calls the garbage collector, it has set
the PB_ACTIVE_WRITER flag in the ProcBin for the binary object
is about to be appended to. Therefore, it is expected that the
garbage collector should neither move nor shrink the binary
object.
But if the garbage collector does a minor collection (thereby
clearing the PB_ACTIVE_WRITER flag in the ProcBin) and there is
still not enough heap space, there will be a second major
garbage collection. During the major collection (since the
the PB_ACTIVE_WRITER flag was cleared), the binary object may
be shrunk or moved (depending on sizes and how many other
writable binaries there are in the process).
Avoid the problem by clearing the PB_ACTIVE_WRITER flags in
a separate pass after the garbage collection(s).
Thanks to Denis Titoruk for helping us find this bug.
|
|
|
|
* Don't redfine ALIGN_BITS or ALIGNED_SIZE, the global defined MSEG_*
constants are just as good.
|
|
|
