| Age | Commit message (Collapse) | Author |
|---|
|
ssh_to_openssh_SUITE:erlang_server_openssh_client_renegotiate/1
|
|
|
|
|
|
The testcases shell_unicode_string and shell_no_unicode in ssh_basic_SUITE could
raise an exception in the end_per_suite when stopping the dameon. This is due to
a natural race condition between the server and the client.
|
|
|
|
in ssh_to_openssh_SUITE:erlang_server_openssh_client_renegotiate/1
The reason is that it seems that on some small machines
we get an out-of-memory exception if the limit is to high.
This is probably because a chunk of data larger than the limit
is piped from a file into the OpenSSH runing in a shell in a port.
|
|
|
|
Funs must not be created in guards. The instruction for creating
a fun clobbers all X registers, which is a bad thing to do in
a guard.
|
|
Avoid suspending fun caller not just if purge is already done
but also if purge of another module has started. Another purge
of the same module again cannot happen as making current to old
transition includes thread progress.
|
|
* bjorn/compiler/inline_list_funcs/ERL-285/OTP-13985:
Don't let inline_list_funcs degrade optimizations
|
|
* hasse/stdlib/fix_shell_default_doc:
stdlib: Correct shell_default(3)
|
|
|
|
into maint
* lukas/erts/tracing/fix_dead_tracer_check/ERL-274/OTP-13928:
erts: Do tracer liveness check on current tracer
|
|
|
|
Do not start an event timer unless there are no enqueued events.
|
|
Handling of timers and timeouts has been cleaned up
and generalized.
Semantic change regarding state timeout zero:
Previously if one state caused a state timeout zero and
managed to stay in the same state to insert additional
timeout zero(s) in the next state callback invocation, then
there would be only one timeout zero event. The mindset
was that the machine was faster then the timeout zero.
This has changed with the mindset that all state callback
invocations should be independent, so now the machine will
get one state timeout zero event per started state timeout
zero.
Note that just using zero timeouts is fairly esoteric...
|
|
|
|
|
|
|
|
- erldoc-browse: open the manual entry for an MFA in the browser
- erldoc-apropos: list MFAs containing a substring
- erldoc-browse-topic: open user guides in the browser
|
|
|
|
* dgud/wx/scale-factor:
wx: Improve error handling
wx: Add wxWindow:getContentScaleFactor
|
|
* dgud/mnesia/fix-blocked/OTP-13970:
Avoid some error reports when stopping mnesia
mnesia: Fix double blocked tables which could cause a crash
|
|
* dgud/tools/emacs/prefer-space/ERL-1200:
Fix whitespace setting in test files
Fix all whitespace-related issues in erlang.el
|
|
Continuation of the previous commit on test files, which gave
whitespace diffs for tabs vs spaces depending on personal settings.
And we want to encourage space instead of tabs.
|
|
* egil/erl_interface/doc-update/OTP-13980:
erl_interface: Remove CDATA tag except for example code
erl_interface: Remove unused file
erl_interface: Fix broken links in documentation
erl_interface: Fix xmllint problems
erl_interface: Fix editorial changes
erl_interface: Editorial changes
erl_interface: Refactor documentation
|
|
|
|
|
|
|
|
|
|
|
|
|
|
83199af0263 refactored sys_core_fold to break out the code for the
inline_lists_funcs option to its own module. Unfortunately, it also
accidentally turned off compile-time evaluation of calls to BIFs with
wholly or partial constant arguments.
For example, the code for the following funtion gets much worse
when inline_list_funcs is used:
b() ->
R0 = #r{},
R1 = setelement(1+2, R0, "deux"),
R2 = setelement(1+3, R1, "trois"),
R3 = setelement(1+5, R2, "cinq"),
R4 = setelement(1+2, R3, "DEUX"),
R4.
ERL-285
|
|
|
|
* fishcakez/dialyzer/fix_attribute_bug/ERL-283/OTP-13979:
dialyzer: Fix error handling of bad -dialyzer() attributes
|
|
If a dialyzer module attribute references an undefined (local)
function an error tuple is thrown but no caught. This leads to a
'nocatch' error and not the intended "clean" error.
|
|
* sverker/ei_connect_xinit/PR-1202:
use only two low bits of creation
|
|
|
|
|
|
The code contained a lot of unmatched return warnings, mostly in function
calls that were executed only for their side-effects. Also, there were
various places where possible errors were not checked and now they are.
This may cause crashes, both in the ftp testsuite (which I have not run)
and in situations were errors occur but are ignored.
|
|
|
|
|
|
|
|
* gomoripeti/stdlib/ms_fix/PR-1203/OTP-13974:
dbg:fun2ms: allow empty list as head
|
|
* raimo/gen_statem-improvements/OTP-13929:
Fix race condition in cancel_timer/1
Use parameterized types
Implement state timeouts
Improve docs and types
Change state entry events into state enter calls
Improve docs
Improve docs
Implement state entry events
Implement call/3 dirty_timeout
|
|
'raimo/erts/fix-configure-to-check-in-libsct-for-sctp-funcs/ERL-262/OTP-13956' into maint
* raimo/erts/fix-configure-to-check-in-libsct-for-sctp-funcs/ERL-262/OTP-13956:
Configure enable libsctp dependency
Revert "Check libsctp for sctp funcs in configure.in"
|
|
|
|
|
|
|
|
* lukas/erts/etp-disasm:
erts: Add etp-disasm gdb macro
|
