Erlang: What are the strategies to deal with huge SASL crash reports?

Question

When my application crashes, I get a crash report, which takes 5 minutes to scroll. What is the best way to handle this?

Answer 1

You can send an emergency dump to a file. Important information is probably at the top.

You could do what Hynek said above and configure the sasl error log handler for crash dumps: http://erlang.org/doc/man/sasl_app.html

By default, tty is used, which resets to your screen and is not very useful, as you mentioned. But you can specify that he should use sasl_report_file_h instead. Then the dump is written to a file for easier reading.

Additional links:

• Documentation of failure in SASL user's guide - how to read a dump emergencies
• Report Browser utility for Sasl error reporting - it may be useful to find out what if the wrong