| Age | Commit message (Collapse) | Author |
|---|
|
* sverker/is_module_native-trace-bug/OTP-14390:
erts: Fix code:is_module_native for local trace
erts: Move and rename erts_is_native_break()
|
|
Originally, etop would only wait for 1 second after starting the
collection of process info from the observed node. If data was not
received in time, etop would exit with reason 'connection_lost'.
In some cases, however, this timer would expire due to the amount of
processes on the observed node. To avoid this, the timer is now
extended to the same as the update interval, which means that if the
problem occurs, it can be helped by extending the interval time.
|
|
|
|
* Remove edoc comments in ct_netconfc.erl
* Rewrite ct_netconfc.xml to use specs for functions and types
* Add documentation of new functions in ct_netconfc
|
|
Added vim and atom to doc's front page
|
|
Fix typo in child spec for file_server
|
|
Mend p->fvalue leak
|
|
Error when a non-DST time is passed to the httpd_util:rfc1123_date/1 function
OTP-14394
|
|
The test found a bug in v3_kernel_pp which was not
taking into account utf8 atoms. The bug has also
been fixed.
|
|
Make 'slim' slim again
|
|
The following new functions are added to ct_netconfc:
* connect/1,2 - open an SSH connection to a netconf server
* disconnect/1 - close the given SSH connectoin
* session/1,2,3 - open an SSH channel on the give connection and send
'hello' to start a netconf session.
This allows running multiple channels on on SSH connection, realizing
one netconf session per channel. The existing ct_netconfc:open will
always run one channel(session) per SSH connection.
|
|
'modeules' -> 'modules'
Introduced in 3edc6dbf8f150bb6ba7c800ed5cc379771f8b279 (present in 20.0-rc1, but
not in the 19 release series).
|
|
When the server_name_indication is sent automatize the
clients check of that the hostname is present in the
servers certificate. Currently server_name_indication shall
be on the dns_id format. If server_name_indication is disabled
it is up to the user to do its own check in the verify_fun.
|
|
|
|
both together.
Broken in OTP-20.0-rc1 by 7d161f5b475575bd79bd90977b3a79334a8ec658.
|
|
|
|
This happens for instance when a receive_trace is run in the
sys_msg_dispatcher thread when the trace_delivered trace message
is traced.
|
|
Remove unused variable warning in compile_SUITE
|
|
system/doc/reference_manual/: fix a typo
|
|
Fixed typo.
|
|
This reverts commit 4f03eba5294f1c1bc922b07f1267e6b0099fd4b5.
|
|
This reverts commit dc57404252c47520f352834ad9be45ad684f96c9.
|
|
p->fvalue will be set by BIFs that generate exceptions
(such as throw/1), and it will not be cleared before another
exception is generated. Potentially, p->fvalue may contain a
huge term (e.g. after throw(HugeTerm)) which will be kept in
the heap.
We can shorten the lifetime of f->value by clearing it in
the instructions that handle catches: catch_end and try_end.
That is safe because BEAM code will never access p->fvalue.
If BEAM code needs to rethrow an exception it will use a
reference to the value passed in an X register.
The reason that p->fvalue must not be cleared already in
handle_error() is that native code trap handlers will use
it. (See the comment before handle_error() and the comment
at the end of handle_error() in beam_emu.c for some more
information about exception handling.)
|
|
|
|
The undocumented compiler option 'slim' is used when compiling
the primary bootstrap. The purpose is to make the bootstrap smaller
and to avoid unnecessary churn in the git repository. That is,
the BEAM file should be different only if the actual code in the
file is different, and not if it has merely been re-compiled on
a different computer.
Two commits have fattened the 'slim' option. In 36f7087ae0f,
extra chunks are included even in slim BEAM files. In dfb899c0229f7,
the "Dbgi" were added as an extra chunk, causing it to be included
in slim files.
Make 'slim' slim again by only including the essential chunks and
the attribute chunk (as was the case before the {extra,...} option
was added).
|
|
|
|
Try doing three consecutive chunked receive with some changed timing in the ending sequence
|
|
|
|
|
|
|
|
Local trace on first function in module
made code:is_module_native/1 return true.
Use new erts_is_function_native() to make a proper check.
|
|
|
|
|
|
|
|
When removing typer as application, it was also removed from the list
of applications to exclude from upgrade tests. However, since typer
still exist in older OTP releases, it must remain in the exclude list
as long as these releases are used in the test.
|
|
|
|
|
|
* IPv6 address FFFF::192.168.42.2 is an invalid form as an IPv4-mapped address.
This should be fixed as ::FFFF:192.168.42.2.
The assigned address block is ::ffff:0:0/96.
See RFC6890 Table 20 in the Section 2.2.2 for the further details.
And for this IPv4-mapped address use *only*,
the 32bit LSB of the IPv6 address can be written
with the respective IPv4 address.
See RFC4291 Section 2.2 Form 3 for the further details.
|
|
|
|
|
|
* rand/arbitrary_normal_distributions:
Disable heavy test case
|
|
* raimo/rand-dev/OTP-14295:
Adjust timetrap
|
|
|
|
* dgud/mnesia/snmp-sup:
mnesia: Remove not used mnesia_snmp_sup
Do not call which_applications()
|
|
* ingela/ssl/releasenote-fix:
ssl: Move missing release note fix to correct place
|
|
Commit 87584ae85893df917ca83cb0c40748fd4da0f3bc added missing release note
but not in the correct place.
|
|
|
|
in the httpd_util:rfc1123_date/1 function.
|
|
* ingela/ssl/missing-relnote:
ssl: Add missing release note
|
|
|
