some time you get many errors on Error Report that told you there is a core dump file and you don’t know where is the problem??
and if you try to read this file you will see a binary codes appear to you and it’s useless information like this :
#more PATH_OF_CORE_FILE l-0.ashr.o��0ذoر^Av�ِ8��BM-^T/lib/core.o�,ز+q^K �ِ�M-^F^X^CZ�/lib/core.o,ذWء^AF6ِ#ه_l/lib/core.o<!?� غ>!\,و^A5M-^@!80^G}M-^F![eP�0D!2ذ^ EX�!]zM-^@M-^PM-^@<!2M-^@HM-^_!^=pR<!1ِM-^@~!_M-^_h^]��<!)M-^Z^N!^M-^U@�t<!' ^A��!
so, there is a nice command that tell you on which module that core dump appear like this :
#lquerypv -h PATH_OF_CORE_FILE 6b0 64 020006C0 7FFAFFFD DFFAFFFF 7FFFFAFF FFAFFFFD |...........| 000002C0 00000004 000186A0 7FFAFFFF FFAFFFFF |...........| 000D06D0 003F0000 8303B820 00002000 3000000C |.?..... ...| 000006E0 6462646B 65796D67 720D0200 30000200 |dbkeyrora..| 000006F0 00020000 01000000 02000300 0000D000 |...........| 00D00700 00D00040 00@0D000 000D0000 03001D61 |..........a| 00000710 00002000 00000014 00003000 03001D61 |..........a|
from the previous output you can know the problem was on module “dbkeyrora” so you can contact your support or tell DB Administrator or Application Administrator
it’s dependence where you find the core dump file.
Summary :
To find out which application crashed the OS use:
# /usr/sbin/lquerypv -h /path/to/core 6b0 64