Erlang: What are strategies for dealing with huge SASL crash dumps?

Question

When my app crashes, I get a crash report that takes 5 minutes to scroll by. What's the best way to handle this?

Answer 1

Just configure your logger.

Answer 2

You could pipe the crash dump to a file. The important information is probably at the top.

You could do what Hynek was saying above and configure a sasl error logger handler for the crash dumps: http://erlang.org/doc/man/sasl%5Fapp.html

The default is tty which dumps to your screen and is not terribly helpful as you mentioned. But you could specify that it should use the sasl_report_file_h instead. Then the dump gets logged to a file for easier perusal.

Additional Links:

• Crash Report documentation in the SASL user guide - how to read a crash dump
• Report Browser utility for Sasl error reports - might be useful for finding out what when wrong