This is the only namespace intended for users. Provides functionality to connect to the debugger and instrument forms.
This is the only namespace intended for users. Provides functionality to connect to the debugger and instrument forms.
Used for remote connections to check this ns has been loaded
Used for remote connections to check this ns has been loaded
(cli-run {:keys [instrument-ns excluding-ns require-before fn-symb fn-args
profile verbose? styles theme flow-id excluding-fns]
:as opts})
Require fn-symb
ns, instrument ns-set
(excluding excluding-ns
) and then call (apply fn-symb
fn-args
).
profile
(optional) should be :full (for full instrumentation) or :light for disable #{:expr :binding}
require-before
(optional) should be a set of namespaces you want to require before the instrumentation.
verbose?
(optional) when true show more logging.
styles
(optional) a file path containing styles (css) that will override default styles
cli-run is designed to be used with clj -X like :
clj -X:dbg:inst:dev:build flow-storm.api/cli-run :instrument-set '#{"hf.depstar"}' :fn-symb 'hf.depstar/jar' :fn-args '[{:jar "flow-storm-dbg.jar" :aliases [:dbg] :paths-only false :sync-pom true :version "1.1.1" :group-id "com.github.jpmonettas" :artifact-id "flow-storm-dbg"}]'
if you want to package flow-storm-dbg with depstar traced.
Require `fn-symb` ns, instrument `ns-set` (excluding `excluding-ns`) and then call (apply `fn-symb` `fn-args`). `profile` (optional) should be :full (for full instrumentation) or :light for disable #{:expr :binding} `require-before` (optional) should be a set of namespaces you want to require before the instrumentation. `verbose?` (optional) when true show more logging. `styles` (optional) a file path containing styles (css) that will override default styles cli-run is designed to be used with clj -X like : clj -X:dbg:inst:dev:build flow-storm.api/cli-run :instrument-set '#{"hf.depstar"}' :fn-symb 'hf.depstar/jar' :fn-args '[{:jar "flow-storm-dbg.jar" :aliases [:dbg] :paths-only false :sync-pom true :version "1.1.1" :group-id "com.github.jpmonettas" :artifact-id "flow-storm-dbg"}]' if you want to package flow-storm-dbg with depstar traced.
(current-stack-trace)
(instrument* config form)
(instrument-namespaces-clj prefixes)
(instrument-namespaces-clj prefixes opts)
Instrument all forms, in all namespaces that matches prefixes
.
prefixes
is a set of ns prefixes like #{"cljs.compiler" "cljs.analyzer"}
opts
is a map containing :
- :excluding-ns a set of strings with namespaces that should be excluded
- :disable a set containing any of #{:expr :binding :anonymous-fn}
useful for disabling unnecesary traces in code that generate too many traces
- :verbose? when true show more logging
Instrument all forms, in all namespaces that matches `prefixes`. `prefixes` is a set of ns prefixes like #{"cljs.compiler" "cljs.analyzer"} `opts` is a map containing : - :excluding-ns a set of strings with namespaces that should be excluded - :disable a set containing any of #{:expr :binding :anonymous-fn} useful for disabling unnecesary traces in code that generate too many traces - :verbose? when true show more logging
(instrument-namespaces-cljs prefixes)
(instrument-namespaces-cljs prefixes opts)
Like flow-storm.api/instrument-namespaces-clj
but for using it from the shadow Clojure repl.
Arguments are the same as the Clojure version but config
also accepts a :build-id
Like `flow-storm.api/instrument-namespaces-clj` but for using it from the shadow Clojure repl. Arguments are the same as the Clojure version but `config` also accepts a `:build-id`
(instrument-var-clj var-symb)
(instrument-var-clj var-symb config)
Instruments any var.
Lets say you are interested in debugging clojure.core/interpose you can do :
(instrument-var-clj clojure.core/interpose)
Then you can call :
(interpose :a [1 2 3])
and it will show up in the debugger.
Be careful instrumenting clojure.core functions or any functions that are being used by repl system code since can be called constantly and generate a lot of noise.
Use uninstrument-var-clj
to remove instrumentation.
opts
is a map that support :flow-id and :disable
See instrument-namespaces-clj
for :disable
Instruments any var. Lets say you are interested in debugging clojure.core/interpose you can do : (instrument-var-clj clojure.core/interpose) Then you can call : (interpose :a [1 2 3]) and it will show up in the debugger. Be careful instrumenting clojure.core functions or any functions that are being used by repl system code since can be called constantly and generate a lot of noise. Use `uninstrument-var-clj` to remove instrumentation. `opts` is a map that support :flow-id and :disable See `instrument-namespaces-clj` for :disable
(instrument-var-cljs var-symb)
(instrument-var-cljs var-symb config)
Like flow-storm.api/instrument-var-clj
but for using it from the shadow Clojure repl.
Arguments are the same as the Clojure version but config
also accepts a :build-id
Like `flow-storm.api/instrument-var-clj` but for using it from the shadow Clojure repl. Arguments are the same as the Clojure version but `config` also accepts a `:build-id`
(local-connect)
(local-connect config)
Start a debugger under this same JVM process and connect to it.
This is the recommended way of using the debugger for debugging code that generates a lot of data since data doesn't need to serialize/deserialize it like in a remote debugging session case.
config
should be a map containing :
- `:verbose?` to log more stuff for debugging the debugger
- `:theme` can be one of `:light`, `:dark` or `:auto`
- `:styles` a string path to a css file if you want to override some started debugger styles
Use flow-storm.api/stop
to shutdown the system nicely.
Start a debugger under this same JVM process and connect to it. This is the recommended way of using the debugger for debugging code that generates a lot of data since data doesn't need to serialize/deserialize it like in a remote debugging session case. `config` should be a map containing : - `:verbose?` to log more stuff for debugging the debugger - `:theme` can be one of `:light`, `:dark` or `:auto` - `:styles` a string path to a css file if you want to override some started debugger styles Use `flow-storm.api/stop` to shutdown the system nicely.
(read-ctrace-tag form)
(read-rtrace-tag form)
(read-rtrace0-tag form)
(read-rtrace1-tag form)
(read-rtrace2-tag form)
(read-rtrace3-tag form)
(read-rtrace4-tag form)
(read-rtrace5-tag form)
(read-tap-stack-trace-tag form)
(read-tap-tag form)
(read-trace-tag form)
(remote-connect config)
(runi opts form)
Run instrumented.
(runi opts form)
Instrument form and run it for tracing.
Same as doing #rtrace form
.
opts
is a map that support the same keys as instrument-var
.
Run instrumented. (runi opts form) Instrument form and run it for tracing. Same as doing #rtrace `form`. `opts` is a map that support the same keys as `instrument-var`.
(stop)
(uninstrument-namespaces-clj prefixes)
Undo instrumentation made by flow-storm.api/instrument-namespaces-clj
Undo instrumentation made by `flow-storm.api/instrument-namespaces-clj`
(uninstrument-namespaces-cljs prefixes config)
Like flow-storm.api/uninstrument-namespaces-clj
but for using it from the shadow Clojure repl.
Arguments are the same as the Clojure version but config
also accepts a :build-id
Like `flow-storm.api/uninstrument-namespaces-clj` but for using it from the shadow Clojure repl. Arguments are the same as the Clojure version but `config` also accepts a `:build-id`
(uninstrument-var-clj var-symb)
Remove instrumentation given a var symbol.
(uninstrument-var-clj var-symb)
Remove instrumentation given a var symbol. (uninstrument-var-clj var-symb)
(uninstrument-var-cljs var-symb config)
Like flow-storm.api/uninstrument-var-clj
but for using it from the shadow Clojure repl.
Arguments are the same as the Clojure version but config
needs a :build-id
Like `flow-storm.api/uninstrument-var-clj` but for using it from the shadow Clojure repl. Arguments are the same as the Clojure version but `config` needs a `:build-id`
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close