| Age | Commit message (Collapse) | Author |
|---|
|
|
|
* 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.
|
|
|
|
|
|
* 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.
|
|
* ph/erl_interface/check-thread-support/OTP-10581:
Teach erl_interface configure more pthread support
|
|
* rickard/native-doc/OTP-10557:
Add clearer warnings about misuse of NIF and driver functionality
|
|
* rickard/ets-mem-bug/OTP-10558:
Fix erlang:memory(ets)
|
|
|
|
|
|
- Teach lib/erl_interface/configure.in to look for
pthreads support in libc (where it can be found on QNX)
- A minor tweak such that this configure *fails* if you pass --enable-threads and
no pthreads support can be found.
|
|
Previously done for ppc in c469d8ce14e9544a297d9af48c9da43137122d9a
|
|
|
|
* sverk/halfword-valgrind-suppressions:
crypto: Add valgrind suppression for AES_cbc_encrypt
erts: Expand valgrind suppression for zlib
Add extra valgrind suppression file for halfword emulator
|
|
* rickard/port-sched-bug/OTP-10556:
Fix bug in erts_port_task_schedule()
|
|
* rickard/sched-wakeup/OTP-10476:
Use reduction limit in order to determine when to do wakeup
|
|
* bjorn/erts/binary-append/OTP-10524:
Fix binary append exceptions
|
|
|
|
|
|
Code such as the following should cause an exception:
Bin = <<0:1>>,
<<Bin/binary,...>>
(Because the "binary" type implies that the binary must have a
size in bits that is a multiple of 8.)
Depending on the binary, either no exception was thrown or the
wrong exception was thrown (because c_p->freason was not set).
Noticed-by: Adam Rutkowski
|
|
* lukas/rcs-ppc-cross-tests/OTP-10265:
Skip ct_netconf tests if there is no crypto
Migrate timers from test_server to ct interface
Update tests to run with an oldshell emulator
Move crypto check so that tc is skipped and not failed
Update for new version of ppc compilation chain
Verify that ebin folder of applications exists
|
|
* egil/ensure-erl_crash.dump/OTP-10422:
test: Relax timeouts for heart_SUITE
erts: Fix crash dump write to port hack
erts: Fix lock check assertion
doc: Document ERL_CRASH_DUMP_SECONDS behaviour
test: Add test for heart restart on crash
test: Add test for heart restart on crash
erts: Change ERL_CRASH_DUMP_SECONDS behaviour
test: Refactor away ?line macros in heart_SUITE
erts: Search for heart in ports that are alive
heart: Refactor heart debugging
erts, heart: Ensure erl_crash.dump is written
|
|
Invalid write of size 8
(Address 0x84a63c0 is not stack'd, malloc'd or (recently) free'd)
Suspected: AES_cbc_encrypt:??? (-> 0xD7489CF) [/lib/libcrypto.so.0.9.8]
|
|
More future proof with R16
|
|
|
|
* heart reboot behaviour
* erl_crash.dump file write behaviour
|
|
to work even when compiler does aggressive function inlining
|
|
Not setting ERL_CRASH_DUMP_SECONDS will now terminate beam
immediately on a crash without writing a crash dump file.
Setting ERL_CRASH_DUMP_SECONDS to 0 will also terminate beam
immediately on a crash without writing a crash dump file, i.e. same as not
setting ERL_CRASH_DUMP_SECONDS environment variable.
Setting ERL_CRASH_DUMP_SECONDS to a negative value will let the beam wait
indefinitely on the crash dump file being written.
Setting ERL_CRASH_DUMP_SECONDS to a positive value will let the beam wait
that many seconds on the crash dump file being written.
A positive value will set both an alarm in beam AND a heart timeout for restart
if heart is running.
This is due to the change of 'heart' behavior when 'heart' is
listening for a crash.
|
|
|
|
|
|
When a crash dump is about to be written and we have
heartbeat enabled on a system. We need time to write it
before heart explicitly kills the beam.
|
|
* egil/fix-boot_combo-test:
test: Fix smoke_test_SUITE
|
|
* lukas/erts/whitespace_nsis_fix/OTP-10481:
Fix bug when making nsis target
|
|
* Skip boot_combo tests where cannot start slave nodes
(The binary will not exist)
|
|
|
|
|
|
|
|
Sometime in cross environments the documentation will
create the lib folders, but there will be no ebin so
all undefined functions should then be ignored.
|
|
* egil/fix-configure-openbsd/OTP-10395:
Fix linking of shared libraries on OpenBSD
|
|
|
|
|
|
* sverk/gcc-atomic-config-bug:
erts: Fix gcc atomic bug in ethread.h
OTP-10418
|
|
* lukas/erts/win32_flush_console_io/OTP-10325:
Make sure io is flushed when driver is closed
|
|
Reported-by: Matthew Dempsky
|
|
|
