Erlang Crash Dump Viewer真的是排错的天兵神器,还记得我们之前曾经讨论过[Erlang 0013]抓取Erlang进程运行时信息 [Erlang 0012]Erlang Process input queue ,下面是我梳理的"How to interpret the Erlang crash dumps"的文档;

 

很多人在问有什么工具可以打开crash_dump文件?或者分析crash_dump文件,其实相当简单,一句命令即可:

1> crashdump_viewer:start().
WebTool is available at http://localhost:8888/

  

Google Reader停了,YUNIO免费服务也停了,这年头没有什么服务是靠谱的,说停就停,下面的链接全是失效了,我重新上传了一份:

http://files.cnblogs.com/me-sa/Erlang_Crash_Dump.pdf

用recon的erl_crashdump_analyzer.sh使用方法如下:

项目地址:   https://github.com/ferd/recon/blob/master/script/erl_crashdump_analyzer.sh

 $ ./recon/script/erl_crashdump_analyzer.sh erl_crash.dump 
 analyzing erl_crash.dump, generated on: Thu Apr 17 18:34:53 2014 
 Slogan: eheap_alloc: Cannot allocate 2733560184 bytes of memory 
 (of type "old_heap"). 
 Memory: 
 === 
 processes: 2912 Mb 
 processes_used: 2912 Mb 
 system: 8167 Mb 
 atom: 0 Mb 
 atom_used: 0 Mb 
 binary: 3243 Mb 
 code: 11 Mb 
 ets: 4755 Mb 
 --- 
 total: 11079 Mb 
 Different message queue lengths (5 largest differen t): 
 === 
 1 5010932 
 2 159 
 5 158 
 49 157 
 4 156 
 Error logger queue length: 
 === 
 0 
 File descriptors open: 
 === 
 UDP: 0 
 TCP: 19951 
 Files: 2 
 --- 
 Total: 19953 
 Number of processes: 
 === 
 36496 
 Processes Heap+Sta ck memo ry siz es (wor ds) us ed in the VM (5 largest 
 different): 
 === 
 1 284745853 
 1 5157867 
 1 4298223 
 2 196650 
 12 121536 
 Processes OldHeap memory sizes (words) used in the VM (5 largest 
 different): 
 === 
 3 318187 
 9 196650 
 14 121536 
 64 75113 
 15 46422 
 Process States when crashing (sum): 
 === 
 1 Garbing 
 74 Scheduled 
 36421 Waiting 
------------------------------------------------------------

  

 

 

官方地址是:http://www.erlang.org/doc/apps/erts/crash_dump.html 

思维导图地址:http://d.yun.io/Q5fY7b

PDF地址:http://d.yun.io/Q5fY7b