Age | Commit message (Collapse) | Author |
|
Use init:get_argument(home) to find the location of the home
directory. That will work on all platforms (including Windows).
Note that the run-time system will fail to start if HOME
(or the equivalent on Windows) is not set. Therefore, it can
be assumed that init:get_argument(home) will not fail.
ERL-161
|
|
In the observer UI, when inspecting state, the error given when attempting to convert a bad term contains a spelling mistake.
|
|
Fix observer application crash
When clicking an HTML-link to a port before the port tab has been opened for the first time, observer would crash since port info is not initiated. This is now corrected.
Also, when clicking on an HTML link to a port, and the port does not exist,
then pop up an info dialog saying "No such port".
OTP-14151
|
|
* siri/cdv/multi-line-slogan/ERL-318/OTP-14093:
[crashdump_viewer] Allow multiple lines in Slogan
|
|
* siri/etop/cpu-per-interval/OTP-14090:
[etop] Show CPU utilization for last interval only
|
|
|
|
Since commit 265998a7e412cd382315632964846569c370a5a2, etop reports
the CPU (scheduler) utilization since the tool was started instead of
for the last interval only. This is now corrected.
|
|
|
|
|
|
* siri/observer/more-port-info/ERL-272/OTP-13948:
[observer] Fix update of range in memory allocator graphs
[observer] Add more port information
[observer] Show monitored ports in process details view
|
|
* siri/cdv/abort-tag/OTP-14053:
[crashdump_viewer] Display abort reason when truncated
|
|
* siri/cdv/faulty-column-vals/OTP-14064:
[crashdump_viewer] Show correct values for 'Object' and 'Memory'
|
|
|
|
|
|
This is a bugfix. Prior to this, only monitored processes were listed
under "Monitored" in the process details view. Now ports are also
shown.
|
|
If a crashdump is truncated due to size limit reached, a new 'abort'
tag with reason is added at the end of the crashdump. This reason is
now displayed along with the truncated-warning.
|
|
* siri/observer/cdv-no-distribution/OTP-14010:
[observer] Start crashdump_viewer in a non-distributed node
|
|
A bug caused the numer of buckets to be shown in the 'Objects' column,
and the number of objects to be shown in the 'Memory' column for ets
table in crashdump_viewer. This is now corrected.
|
|
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.
|
|
This sets the maximum queue size for the IP trace driver which is used
when tracing to shell and/or <c>{local,File}</c>.
Also, change the default queue size set by dbg:trace_port/2 to 200.
|
|
|
|
Fix some older errors as well.
|
|
When observing mnesia table on remote node and connection to that node
is lost, a loop of error messages occur if mnesia is not running on
the observer node. ERL-237
|
|
|
|
|
|
Caused a crash in 19, see ERL-171.
Data was never reset so the number of schedulers didn't match the
previous collected data.
|
|
|
|
* josevalim/supervisor-get-callback-module/PR-1000/OTP-13619:
Return callback module in supervisor format_status
|
|
The previous implementation of supervisor:get_callback_module/1
used sys:get_status/1 to get the supervisor inner state and
retrieve the callback module. Such implementation forbids any
other supervisor implementation that has an internal state
different than the #state{} record in supervisor.erl.
This patch allows supervisors to return the callback module
as part of the sys:get_status/1 data, no longer coupling the
callback module implementation with the inner #state{} record.
Notice we have kept the clause matching the previous
sys:get_status/1 reply for backwards compatibility purposes.
|
|
|
|
This reverts commit e020f75c10410a6943cd055bfa072a2641eab7da.
|
|
|
|
* siri/observer/improve-trace/OTP-13481:
[observer] Update user guide
[observer] Automatically add active node
[observer] Allow more trace flags on procs/ports from GUI
[runtime_tools] Don't trace the trace client port
[runtime_tools] Allow setting trace flag 'exiting' with dbg
[observer] Add more default match specs for messages
[observer] Add test of new Ports tab
[observer] Improve appearance in Trace tab
[observer] Allow multiple select in Ports tab
[observer] Make right click menu act on the "expected pid"
[observer] In Trace tab, show procs/ports for selected node only
[observer] Add right click menu in Table tab
[observer] Add menu option to set default MS for send/receive
[observer] Add tracing of ports
[ttb] Allow setting trace flags on ports
[observer] Set correct parent in Label dialog
[observer] Add Ports tab in GUI
[observer] Add functionality in GUI for trace pattern on messages
[ttb] Set trace patterns on messages
Conflicts:
lib/observer/src/observer_wx.erl
|
|
Document the new Ports tab and tracing of ports.
|
|
When setting trace flags on 'new_processes' or 'new_ports', the
currently active node is now automatically added if no other node is
traced.
|
|
|
|
|
|
|
|
* Only allow single selection of modules
* Add right click menu to remove module
* Allow multiple selection of nodes, and show procs/ports for ALL
selected nodes
* On right click, only show menu items that make sense for the current
content and selection
* Add tooltips with help text
|
|
This is helpful when selecting ports to be traced.
|
|
If multiple processes were selcted, "Process Info" and "Kill Process"
menu choices would pick the first pid in the selection list, i.e. the
last selected process. This is now changed so the process under the
mouse pointer is used instead.
|
|
Earlier, all traced processes and ports would be shown, independent of
selected nodes in node view. This is now corrected.
|
|
|
|
|
|
|
|
|
|
The dialog for setting label on match specs in observer had faulty
parent. This is now corrected.
|
|
|
|
|