Age | Commit message (Collapse) | Author |
|
|
|
|
|
This is a bugfix. Prior to this, only monitored processes were listed
under "Monitored" in the process details view. Now ports are also
shown.
|
|
Fix FSF mail address
|
|
* siri/observer/cdv-no-distribution/OTP-14010:
[observer] Start crashdump_viewer in a non-distributed node
|
|
* siri/observer/remove-unused-files/OTP-14024:
[observer] Remove unused files
|
|
* leoliu/tools/fix_edoc_mode:
Fix font-locking for @deprecated in erlang-edoc-mode
|
|
* victorhge/tools/emacs/icr_indentation/PR-1193:
Add an option erlang-icr-indent
|
|
* dgud/wx/gl-bugs:
wx: Do not dispatch commands after frequent events
Avoid unnecessary length calculations in gl
Add option to send prebuilt binaries to multiDrawArrays
Fix gl driver pointer error
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* margnus1/hipe-call-elim-crash/PR-1253:
hipe_icode_call_elim: Fix cf elimination crash
hipe: Improve error message on internal crashes
|
|
* bjorn/compiler/fix-unwanted-warning/ERL-301/OTP-14040:
Suppress warnings from v3_kernel when inlining is turned on
|
|
* jimdigriz/kernel/rpc-doc/ERL-302/PR-1252:
document {yield/nb_yield}() limitation
|
|
* hasse/dialyzer/improve_messages/OTP-11403:
dialyzer: Substitute 'opacity' for 'opaqueness'
dialyzer: Improve a warning message
dialyzer: Improve a warning message
dialyzer: Correct a warnings message
|
|
* hasse/stdlib/correct_types:
stdlib: Correct types of the abstract format
|
|
The types in erl_parse.yrl are more in harmony with the description in
The Abstract Format (in ERTS User's Guide).
|
|
|
|
The user app may want to handle several mouse motion events before
drawing new data for example.
|
|
|
|
|
|
Suggested by Kostis.
|
|
Messages regarding guards with orelse/andalso could look
like "Clause guard cannot succeed. The variable A was matched
against the type any()". Now they look like as if or/and is
used: "Guard test is_integer(A::atom()) can never succeed".
|
|
Messages like "Invalid type specification for function
para3:exp_adt/0. The success typing is () -> 3" now look like
"The specification for para3:exp_adt/0 has an opaque subtype
para3_adt:exp1(para3_adt:exp2()) which is violated by the success
typing () -> 3".
The old message did not give any clue as to what invalidated the
contract, namely the opaque subtype.
|
|
Messages like "The attempt to match a term of type rec_api:f()
against the variable _ breaks the opaqueness of rec_adt:f()" now
look like "The attempt to match a term of type rec_adt:f()
against the record field 'f' with type rec_api:f() breaks the
opaqueness of the term".
|
|
|
|
For lists the pointer was not advanced as it should which caused
following in-data (if any) to be wrong.
|
|
|
|
|
|
deleted: priv/crashdump_viewer.tool
deleted: priv/crashdump_viewer/collapsd.gif
deleted: priv/crashdump_viewer/exploded.gif
|
|
The shell script (priv/bin/cdv) and bat file (priv/bin/cdv.bat) which
can be used for starting crashdump_viewer both started a distributed
erlang node. This would cause any attempt at starting a second
instance of the crashdump_viewer to fail. To solve this problem, cdv
and cdv.bat now use non-distrubuted nodes when starting the
crashdump_viewer.
|
|
hipe_icode_call_elim could in some cases replace an #icode_call{} with
control flow with a move instruction. This would break the control flow
graph invariants and cause a crash.
|
|
Print the MFA/module being compiled, and pretty-print the backtrace with
lib:format_stacktrace/4.
Additionally, make the error_msg/2 macro in hipe.hrl respect the
HIPE_LOGGING define, since messages produced by this macro just before
runtime shutdown were sometimes lost (since code_server:error_msg/2 is
asynchronous).
|
|
|
|
The option makes it possible to customize the indention of
if/case/recieve patterns.
Before the change, the indentation of 'if' patterns is 3 steps and
'case' patterns is 4 steps. It cannot be changed alone. Some people
prefer other styles, for example, zero indentation.
case a of
true ->
do_something();
false ->
do_something_else()
end.
This patch just adds an option `erlang-icr-indent'. Its default value is
`nil' which means keeping the legacy behavior. When non-nil, the
pattens of if/case/receive are indented according to
`erlang-icr-indent'. "(setq erlang-icr-indent 0)" will keep
if/case/receive at the same column of the sub-clauses.
Change-Id: I10c32e42dbf69cbe187f55223b9aa7824853e493
|
|
|
|
The rfc 4255 is about fingerprints, but only in the context of dns. Since this is out-of-scope for the Erlang/OTP ssh, the reference is missleading.
|
|
|
|
|
|
|
|
* bjorn/cuddle-with-tests:
Correct tar_SUITE:unicode/1
|
|
* ingela/httpc/keep-alive-https/OTP-14041:
inets: httpc - do not send absolute URIs over TLS tunnels
|
|
v3_kernel may produce unwanted and confusing warnings for code that
has been inlined with the new inliner (cerl_inline). Consider this
code:
-compile(inline).
compute1(X) ->
add(X, 0).
compute2(X, Y) ->
add(X, Y).
add(1, 0) ->
1;
add(1, Y) -> %% "this clause cannot match..."
1 + Y;
add(X, Y) ->
X + Y.
v3_kernel warns because add/2 has been inlined into compute1/1 and only
the first clause in add/2 will match. But the other clauses are needed
when add/2 is inlined into compute2/2, so the user cannot do anything
to eliminate the warning (short of manually inlining add/2, defeating the
purpose of the 'inline' option).
The warning would be reasonable if compute2/2 didn't exist, but it would
be too complicated for the compiler to figure whether a warning make
sense or not.
Therefore, suppress all warnings generated by v3_kernel if cerl_inline
has been run.
ERL-301
|
|
* ingela/odbc/mac:
odbc: Remove support for old MACs
|
|
Change configure to skip odbc for old MACs, the change in
PR-1227 is not backwards compatible with old MACs, and we do not
see a need to continue support for such old versions. However
it is still possible to make it work on such machines using
the --with-odbc configure option.
|
|
Make sure that we always test the "+fnu" option on all
systems. It seems that it was not tested in our daily
builds, since they are run non-interactively.
Make sure that we sort the list of names in do_unicode/1.
Otherwise the test would only work in "+fnl" mode because
the list would only contain one element.
|