| Age | Commit message (Collapse) | Author |
|---|
|
Plan to make use of the emulator restart implied by a major release to
clean out some upgrade-related code.
|
|
* lukas/17/docfixes/OTP-11613:
17.0 anchor and broken links fixes
|
|
The type's existence is the subject of OTP-11139, which has been
gathering dust since R16B.
http://erlang.org/pipermail/erlang-bugs/2013-September/003765.html
|
|
* rickard/load_balance/OTP-11385:
Fix usage of non-empty run-queue flag
|
|
|
|
OTP-10907
|
|
OTP-10877
OTP-10907
|
|
|
|
Mainly mac stuff
|
|
Should not call showModal on a wxProgressdialog it is already display
(see doc) and it hangs on MacOSX until someone presses the menu.
|
|
|
|
* bugfixes
* add first test
* remove unused code
|
|
|
|
Fix app viewer crash
|
|
Use arrays instead of lists to cache data, gives faster lookups for
large contents.
Also update colors used in table viewer, indication new and changed rows.
Other minor bugfixes in tables viewer.
|
|
* bugfixes
* better progress dialogs
* show expanded binaries in different formats
* speed up reading of big crashdumps
|
|
Add clickable links to processes in process info
Use html pages (contains clickable processes) to view messages,
dictionary and other information.
|
|
The old web base crashdump_viewer is now removed.
|
|
* lukas/erts/sendfile_passive_mode_fix/OTP-11614:
erts: fix bug when using passive mode and sendfile
|
|
The bug incorrectly issued driver_select when un-ignoring an fd
for a socket in passive mode, which caused an incorrect error
tuple to be returned when the remote end closed the connection.
|
|
* lukas/17/docfixes/OTP-11613:
system: Fix documentation typoes
|
|
|
|
* dgud/wx/refactor-and-bugfixes/OTP-11586:
wx: Delay all deletes if recursed in event loop
wx: wx could hang if wxe_server died (or had died) when inside a callback
wx: Delay memory cleanup until safe
wx: Refactor C++ code
wx: Add init_dialog event
Update icons
wx: Update icons to plain old white ones
|
|
* anders/diameter/sctp_streams/OTP-11593:
Change interface for communicating outbound stream id to diameter_sctp
|
|
* anders/diameter/undefined_group/OTP-11561:
Ensure that Grouped AVP's are fully defined in dictionaries
Don't format diameter_make:codec/2 errors
Compiler suite fix
|
|
* bjorn/compiler/fix-crash/OTP-11610:
beam_except: Eliminate compiler crash
|
|
We can't recommend -on_load() for general use.
|
|
|
|
Code such as:
bar(X) ->
case {X+1} of
1 -> ok
end.
would crash the beam_except pass of the compiler.
The reason for the crash is that the '+' operator would add a line/1
instruction that the beam_except pass was not prepared to handle.
Reported-by: Erik Søe Sørensen
|
|
The module uses the transport_data field of record diameter_packet to
communicate the stream on which the an incoming message is received and
on which an outgoing message should be sent, the previous interface
being that both are communicated as a tuple of the form {stream, Id}.
However, since diameter retains the value of an incoming request's
transport_data unless the corresponding answer message specifies
otherwise, the behaviour in this case is to send an answer on the
outbound stream with the same identifier as the that of the inbound
stream on which the request was received. If the inbound stream id is
greater than or equal to the number of outbound streams then this is
guaranteed to fail, causing the transport process in question to
terminate. There is no relationship between inbound and outbound stream
identifiers so diameter_sctp's imposition of one is simply wrong.
Outbound stream ids are now communicated with a different tuple:
{outstream, Id}, interpreted modulo the number of outbound streams.
Thus, retention of an inbound request's transport_data has no effect on
the selection of an outbound stream.
The change in interface is not strictly backwards compatible because of
the new atom for the outbound stream. However, as there is currently no
documented way of obtaining the available number of outbound streams for
a peer connection, there is no way for a client to have known the range
of ids from which it could reliably have chosen with the previous
interface, so any setting of the outbound stream has probably been
unintentional. Not explicitly specifying an outbound stream now results
in a round-robin selection.
|
|
* andrewtj/atj-crypto-chiphertext-typo:
crypto: Fix 'ChipherText' typo in doc
OTP-11609
|
|
* oliv3/fix_valgrind_warning_in_gen_challenge:
(memcheck) Uninitialized structure in gen_challenge
OTP-11608
|
|
* blt/doc_language_improvement:
Clean up some awkward wording around the +spp flag.
OTP-11607
|
|
* zaa/docfix:
Typo fix
OTP-11606
|
|
The R16B03-1 release
|
|
* rickard/load_balance/OTP-11385:
Disable scheduler utilization balancing if +scl true is passed
|
|
|
|
|
|
Conflicts:
otp_build
|
|
* ia/ssl/secure-renegotiate/OTP-11595:
ssl: Incorrect inputed cipherlist lead server to think that the client did not support secure renegotiation
|
|
* rickard/load_balance/OTP-11385:
Add support for scheduler utilization balancing
|
|
Avoids crashes.
|
|
* rickard/default_acul/OTP-11604:
erts: Use "+Muacul de" as default
|
|
For more information see documentation of the new command line argument +sub
|
|
* lucafavatella/fix-doc-of-dbg-stop:
Correct doc of return value of dbg:{stop,stop_clear} functions
OTP-11603
|
|
* vinoski/system-flag-warn-msg:
fix system_flag deprecation warnings
OTP-11602
|
|
* vinoski/emacs-fixes:
fix emacs erlang skeleton indentation
fix indentation error from scan-sexp in erlang.el
prevent errors from erlang.el
fix erlang-mode erlang-get-function-arity
OTP-11601
|
|
|
|
|
|
print to screen instead of writing to the file
provided. The reason for this is that you may want
to have an intermediary step between saving the
tidied file and using the output.
Use-case personally is wanting to integrate
erl_tidy into emacs and tidy buffers, overwriting
the current file is generally not how this works
in emacs with source code tidiers.
|
