easco
I have a process, using gen_statem, which was crashing (and being restarted by a supervisor) because of an unhandled exception.
When I first encountered the issue while debugging it was clear that the process was restarting, but the unhandled exception didn’t cause anything to be printed to the console. It would silently fail, the supervisor would restart things, and the cycle would continue.
Tracking down the issue would have been much faster if the exception had been more “noisy”. I tried using the :debug option for my server with both “:trace” and “:log” - while it was interesting to see the system messages the exception was still silently raised and handled.
Is there something I could have done to make the unhandled exception more “noisy”, at least in dev mode, so I could have come to a resolution more swiftly?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
We build reliable cloud platforms for business-critical systems.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Master modern tools, write cleaner code, and tackle real-world challenges.
Producing high quality Elixir screencasts since 2017.
Enabling companies to succeed by building software people love.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
OvermindDL1
Enable the built-in
saslapp, but be warned, it will be VERY noisy. It logs all OTP process creation and crashes and so forth.grzuy
For what is worth, updating this thread after 5 years.
Fortunately now (since Erlang/OTP 21) a new improved
loggerexists, which deprecates thesaslapp.Quote from SASL Error Logging — OTP 29.0.2 (sasl 4.4) as of today: