This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-01-16
Channels
- # aleph (2)
- # announcements (1)
- # aws (2)
- # babashka (5)
- # beginners (122)
- # boot-dev (1)
- # cider (3)
- # clara (7)
- # cljdoc (11)
- # clojure (161)
- # clojure-dev (45)
- # clojure-europe (8)
- # clojure-france (1)
- # clojure-india (1)
- # clojure-italy (3)
- # clojure-nl (11)
- # clojure-uk (34)
- # clojurebridge (2)
- # clojurescript (13)
- # cryogen (10)
- # cursive (13)
- # datomic (25)
- # emacs (8)
- # fulcro (76)
- # graalvm (2)
- # jackdaw (5)
- # jobs-discuss (2)
- # juxt (13)
- # off-topic (13)
- # pathom (5)
- # pedestal (7)
- # quil (2)
- # reitit (9)
- # remote-jobs (4)
- # schema (1)
- # shadow-cljs (33)
- # spacemacs (8)
- # sql (9)
- # vim (2)
- # vrac (2)
I'm running the debugger and have a function like this:
(defn foo
[x]
(+ x "as"))
When I run (foo 1)
in the repl I get a ClassCastException thrown. I have Java Exception Breakpoints > Any exception checked. And a notification for only Uncaught exceptions (the caught exception is unchecked). The debugger does not pause on the ClassCastException with this configuration. Is this expected?No, that should work. If you switch to catching caught exceptions too does that stop?
Hmm, that’s probably because the REPL will catch all exceptions to do error handling, and the debugger knows that.
Could you file an issue about that? I’m not sure I’ll be able to fix that but I’ll try.
Do people typically start their REPL in "debug" mode so you don't need to restart your REPL to activate it when you need it?
I don’t always start a REPL (depends what I’m working on, it’s not always possible/useful), but I always start my app in debug mode, yes.
There’s very little downside. The main problem is that I’ve found that it can greatly increase memory consumption on the launching IDE, but not always.