Age | Commit message (Collapse) | Author |
|
Conflicts:
erts/etc/common/heart.c
|
|
* 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
|
|
* sverk/valgrind-quoting:
Make cerl -valgrind work with quoted spaces in command line
|
|
More future proof with R16
|
|
|
|
* heart reboot behaviour
* erl_crash.dump file write behaviour
|
|
* jf/fix_sctp_peeloff_active_true:
Set new peeled off SCTP socket to nonblocking socket
SCTP test case with socket active options once and true
OTP-10491
|
|
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.
|
|
* lukas/erts/dont_break_reductions_skip/OTP-10373:
Skip dont_break_reductions on hipe libs tests
|
|
* lukas/erts/bad_terms_hipe_skip/OTP-10375:
Skip fun corruption when lists is native
|
|
|
|
This is needed as corruption of the index_uniq byte
can cause very strange behaviour when the fun is called
by native code.
|
|
|
|
* egil/fix-boot_combo-test:
test: Fix smoke_test_SUITE
|
|
* maint:
Fix bug when making nsis target
|
|
* 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)
|
|
* maint:
Add comment about eproviderfailedinit error
Increase sbct for win64 as block alignment is 16
|
|
|
|
|
|
* egil/remove-unused-files:
Remove unused files from old native dns resolver
|
|
Peeloff feature of SCTP association creates a new socket which is not
set to nonblocking.
Function for receving data is shared with udp which has a default
loop when reading packets which is set to 5.
Calling the receive function more then once, is fine as long as
there are more data to receive or socket are nonblocking.
Set new peeled off socket to be nonblocking to prevent a erlang vm hangup.
|
|
* sverk/code-load-refactor-later-op:
erts: Fix faulty lock check assert
erts: Refactor naming regarding code_write_permission
erts: Refactor tracing to use erts_schedule_thr_prgr_later_op
erts: Allow thr_prgr_later_op to reschedule
erts: Refactor code loading to use erts_schedule_thr_prgr_later_op
erts: Remove some compiler warnings
|
|
|
|
|
|
In the erl_crash.dump file, native-compiled modules did not have
any information about attributes and compilation.
The problem is that the code:make_stub_module/3 BIF (which is
internally used when native code is loaded) did not copy the size
field the attribute and compilation info chunks. Those size fields
are only used when writing crash dumps.
|
|
* egil/r16/strengthen-buffer-copies:
Replace sprintf with erts_snprintf in beam
Replace sprintf with erts_snprintf in epmd
Replace sprintf with erts_snprintf in inet_gethost
|
|
|
|
* 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
|
|
* sverk/gcc-atomic-config-bug:
erts: Fix gcc atomic bug in ethread.h
|
|
* maint:
Make sure io is flushed when driver is closed
|
|
* lukas/erts/win32_flush_console_io/OTP-10325:
Make sure io is flushed when driver is closed
|
|
|
|
|
|
|
|
|
|
Reported-by: Matthew Dempsky
|
|
|
|
Sometime when executing an tty io operation just before
the emulator terminated, the io message would get lost.
This commit makes sure that there is no io in the fd driver
before shutting down.
|
|
A faulty #if 0 caused healthy gcc builtin atomic to be ignored.
|
|
The R15B02 release
|
|
|
|
|
|
|