Link to home
Start Free TrialLog in
Avatar of vinodnp
vinodnp

asked on

debugging core files

How can I find out the part of the code which is causing my application to core dump?
Is there a way to interpret or debug the core file itself? I am currently using solaris.
Thanks !
Avatar of yuzh
yuzh

Use:  mdb

man mdb

to learn more, or have a look at the following docs:
http://developers.sun.com/solaris/developer/support/driver/docs/MDB-Sol8.pdf

Or
download gdb from the following site (free):
http://www.sunfreeware.com/

Cheers!
Also a Core Analysis script available on SunSolve - ICDSA.sh, I think.
dbx is another tool, u can use gdb(GNU debug also).
if u want to know how to use it, please let us know.
Application core dumps occures in the directory in which the application binary is run from.
u can use strings command to get the preliminary analysis done. Advanced debugging can be cone by using any of the floowing tools : adb / mdb / dbx / gdb .... depending upon the way the application is designed and your comfort level with these tools.

ISCDA is a shell script which runs adb in the back ground for debugging OS core dumps...not useful for analysing application core dumps.
ASKER CERTIFIED SOLUTION
Avatar of Hanno P.S.
Hanno P.S.
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
you can try using "truss" to see where in your application is dumping core rather then looking at the core file.  sometimes this way is faster and easier.
something like truss -f -p <pid> or truss -p <pid> or truss <application_executable>
the -f follows child processes
Hi,

i was running a huge java application on Solaris 5.8 for performance tuning. After 18 Hours the process exited with a core dump. The dump is from Java program. Can anybody tell me which tool i can use to analyse the core dump.

kiranmaiem,

In EE's culture, its generally considered bad form to piggyback your Question onto another user's Question. You really should open your own Question.