| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
| |
Two drafts have now been RFCs. Only editorial changes in them from implementation point of view.
|
|\
| |
| |
| |
| |
| | |
* rickard/signals/OTP-14589:
Fix seq trace
Fix bad assert
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Run scripts/diffable without arguments to print a description
and a few examples.
|
|\ \
| | |
| | | |
Teach httpc to honour server connection close
|
| | |
| | |
| | |
| | | |
Addresses https://github.com/erlang/otp/pull/1752#discussion_r177970060
|
| | |
| | |
| | |
| | |
| | | |
... addressing PR comment
https://github.com/erlang/otp/pull/1752#pullrequestreview-107945563
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
From https://tools.ietf.org/html/rfc7230#section-6.6
> A client that receives a "close" connection option MUST cease
sending requests on that connection and close the connection after
reading the response message containing the "close"; if additional
pipelined requests had been sent on the connection, the client
SHOULD NOT assume that they will be processed by the server.
Notes on tests:
* The new tests are added only in group sim_http and not sim_https
because the same test approach appears to be not valid because when
processing the first response the server already sent data (> 0) for
the TLS/SSL handshake;
* The order of tests is relevant as it appears some test cases leave
reusable sessions behind.
|
| | |
| | |
| | |
| | |
| | | |
It looks like a typo, though I did not experience impact of this on
tests.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
... i.e. references to `connect_failed` and `send_failed`, unused
since 5d32eaf750 .
|
| | | |
|
|\ \ \
| | | |
| | | | |
Remove note about heart rebooting on NTP updates
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The timestamp code in heart uses monotonic time so it is immune to NTP
changes.
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Reflect actual timer:tc behaviour in documentation
|
|/ / / /
| | | |
| | | |
| | | |
| | | | |
It was switched to monotnic_time from timestamp 3 years ago
in d927209aa36fe370eb4ecf0a081923b0b951458b
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Check that messages outside of the heap are not corrupted
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Waiting messages for a process may be stored in a queue
outside of any heap or heap fragment belonging to the process.
This is an optimization added in a recent major release to
avoid garbage collection messages again and again if there
is a long message queue.
Until such message has been matched and accepted by
the remove_message/0 instruction, the message must not be
included in the root set for a garbage collection, as that
would corrupt the message. The loop_rec/2 instruction explicitly
turns off garbage collection of the process as long messages
are being matched.
However, if the compiler were to put references to a message
outside of the heap in an Y register (on the stack) and there
happened to be a GC when the process had been scheduled out,
the message would be corrupted and the runtime system would
crash sooner or later.
To ensure that doesn't happen, teach beam_validator to check
for references on the stack to messages outside of the heap.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Support dumping of external fun literals to a crash dump
|
| |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
63e1c58d27ab (PR #1725) started to compile external funs
as literals.
This commit updates the dumping of literal areas to dump
external fun literals to the crash dump.
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* maint:
Updated OTP version
Prepare release
ssh: Fix ssh_sftpd:handle_op not returning State
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
* maint-19:
Updated OTP version
Prepare release
ssh: Fix ssh_sftpd:handle_op not returning State
Conflicts:
OTP_VERSION
lib/ssh/doc/src/notes.xml
lib/ssh/vsn.mk
otp_versions.table
|
| | | | | | | |
|
| | | | | | | |
|
| | |\ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
* hans/ssh/sftpd_rm_dir_err_19/OTP-15004:
ssh: Fix ssh_sftpd:handle_op not returning State
|
| | |/ / / / / |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | | |
Doc: use that node name between code and commands
|
|/ / / / / /
| | | | | |
| | | | | | |
The server_node() function in the sample code was referring to messenger@bill, while the commands that follow use messenger@super as node name. Making both names consistent make it easier for newbies to test the code.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix unsafe optimization of record test
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
beam_record would make an unsafe optimization for the
not_used_p/4 function added to beam_utils_SUITE in this
commit. The bug is in beam_utils, which would falsely
report that {x,4} was unused when it in fact was used.
The bug was in the function not_used/1. The purpose of
not_used/1 is to return a 'not_used' result unless the
actual result is 'used'. Unfortunately it was not
implemented in that way. It would let a 'transparent'
result slip through, which the caller in this case would
convert to 'killed' (because the register was killed on
all other paths).
Reported-by: Richard Carlsson
|
|\ \ \ \ \ \ \ |
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
detected by valgrind. We cannot compare monitor
in state MON_FREE before it's initialized.
Still not really kosher to access 'state' without lock or atomic-op.
|
|\ \ \ \ \ \ \ \
| |_|/ / / / / /
|/| | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Compile external fun expressions to literals
OTP-15003
|
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
The expressions fun M:F/A, when all elements are literals are also
treated as a literal. Since they have consistent representation and
don't depend on the code currently loaded in the VM, this is safe.
This can provide significant performance improvements in code using such
functions extensively - a full function call to erlang:make_fun/3 is
replaced by a single move instruction and no register shuffling or
saving registers to stack is necessary. Additionally, compound data
types that contain such external functions as elements can be treated as
literals too.
The commit also changes the representation of external funs to be a
valid Erlang syntax and adds support for literal external funs to core
Erlang.
|
|\ \ \ \ \ \ \ \
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
* lukas/erts/tcp_send_return_closed/OTP-15001:
erts: tcp send should return {error,closed}
|
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | |
| | | | | | | | | |
In the scenario where a gen_tcp:recv/2 detected an
error, the next gen_tcp:send should get a closed
error and not a enotconn error as was the case before.
|
|\ \ \ \ \ \ \ \ \
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | |
| | | | | | | | | | |
* lukas/ei/fix_tmo_test:
ei: Include stdlib.h to fix malloc usage in ei test
|
| | | | | | | | | | |
|
|\ \ \ \ \ \ \ \ \ \
| | | | | | | | | | |
| | | | | | | | | | | |
Split inets OTP-14113
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Change-Id: I014b191da144c299d056eb155ed99ace710112b1
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Change-Id: Ie0f52e82484462f8f7ec58c37ce16081af432797
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Change-Id: Ie23a40e7159fe632cf5514ac617de17c5d5b5ce2
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
- Update ct_ftp to use the new FTP application.
Change-Id: I84223107361132ea3144cdf7421738c4bebffa40
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Change-Id: I585ba5097632d460705257f03cb44adf8038f0be
|
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | |
| | | | | | | | | | | |
Change-Id: I20d44e771577b19060fbba0b2e83f64909c60faa
|