This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-21
Channels
- # alda (1)
- # bangalore-clj (1)
- # beginners (7)
- # boot (88)
- # carry (2)
- # cider (8)
- # cljs-dev (60)
- # cljsjs (2)
- # cljsrn (45)
- # clojure (255)
- # clojure-belgium (5)
- # clojure-boston (1)
- # clojure-dusseldorf (3)
- # clojure-greece (49)
- # clojure-italy (10)
- # clojure-russia (30)
- # clojure-spec (78)
- # clojure-uk (11)
- # clojurebridge (1)
- # clojurescript (80)
- # cursive (14)
- # datomic (33)
- # defnpodcast (4)
- # devcards (2)
- # dirac (15)
- # editors (23)
- # emacs (5)
- # events (11)
- # funcool (1)
- # hoplon (1)
- # juxt (1)
- # luminus (2)
- # mount (7)
- # off-topic (15)
- # om (152)
- # om-next (2)
- # onyx (17)
- # parinfer (1)
- # proton (38)
- # re-frame (35)
- # reagent (110)
- # rum (3)
- # spacemacs (3)
- # specter (51)
- # test-check (2)
- # testing (5)
- # untangled (234)
We have hit the breakpoint at line 437. and this is the UI from intellij that you requested.
I reran, have suspend=y in the jdwp command, so the app breaks waiting for a debugger to attach.
I think maybe the issue is that i have the app built locally with Java 8, but I am remote debugging an app that is running on java7
@bradrhod The problem is that your breakpoint is still stopping in the class initialiser. This is because Clojure executes code very differently to Java.
When a namespace is loaded, the class initialiser will load all the function classes and attach their metadata etc
What you’re seeing is that during that initialisation, the code being executed is the code that actually creates your function and assigns it to a var.