Use rt_config instead of a new ets table for tracing configuration.

Author: andytill

src/riak_test_escript.erl

@@ -214,12 +214,8 @@ parse_command_line_tests(ParsedArgs) ->
     %% this is a little ugly, the process that creates the ets table to store
     %% the tracing state cannot shutdown or the table will be gc'ed, so create
     %% a dummy proc that doens't die
-    proc_lib:spawn(
-        fun() ->
-            rt_redbug:new(),
-            rt_redbug:set_tracing_applied(proplists:is_defined(apply_traces, ParsedArgs)),
-            timer:sleep(infinity)
-        end),
+    rt_redbug:new(),
+    rt_redbug:set_tracing_applied(proplists:is_defined(apply_traces, ParsedArgs)),
     %% Parse Command Line Tests
     {CodePaths, SpecificTests} =
         lists:foldl(fun extract_test_names/2,

src/rt_redbug.erl

@@ -33,14 +33,14 @@
 
 %% Create a new ets to store globally whether we're tracing or not.
 new() -> 
-    rt_trace_tab = ets:new(rt_trace_tab, [named_table]).
+    ok.
 
 set_tracing_applied(TracingApplied) when is_boolean(TracingApplied) ->
     lager:info("Setting apply tracing to ~p", [TracingApplied]),
-    ets:insert(rt_trace_tab, {apply_traces,TracingApplied}).
+    rt_config:set(apply_traces, TracingApplied).
 
 is_tracing_applied() ->
-    (catch ets:lookup_element(rt_trace_tab, apply_traces, 2)) == true.
+    rt_config:get(apply_traces).
 
 %% Apply traces to one or more nodes using redbug tracing and syntax.
 %%