summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSimon MacMullen <simon@rabbitmq.com>2014-11-07 12:20:55 +0000
committerSimon MacMullen <simon@rabbitmq.com>2014-11-07 12:20:55 +0000
commit175173eb54baecd3e166894f4815f1f15d2b9472 (patch)
tree26d5d14c142e21834594cb9409a5a7977c624bf0
parent792be6de739033b17d164328feeedb9c64089f68 (diff)
parente5f7de597c871d9eec60dcdc99265dd4a5d6af56 (diff)
downloadrabbitmq-server-git-175173eb54baecd3e166894f4815f1f15d2b9472.tar.gz
Merge bug26460
-rw-r--r--src/rabbit_diagnostics.erl4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/rabbit_diagnostics.erl b/src/rabbit_diagnostics.erl
index 4eafada3f3..bf45b7575f 100644
--- a/src/rabbit_diagnostics.erl
+++ b/src/rabbit_diagnostics.erl
@@ -41,13 +41,13 @@ maybe_stuck(Pids, Timeout) ->
maybe_stuck(Pids2, Timeout - 500).
looks_stuck(Pid) ->
- case process_info(Pid, status) of
+ case catch process_info(Pid, status) of
{status, waiting} ->
%% It's tempting to just check for message_queue_len > 0
%% here rather than mess around with stack traces and
%% heuristics. But really, sometimes freshly stuck
%% processes can have 0 messages...
- case erlang:process_info(Pid, current_stacktrace) of
+ case catch erlang:process_info(Pid, current_stacktrace) of
{current_stacktrace, [H|_]} ->
maybe_stuck_stacktrace(H);
_ ->