vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello All: I am just wondering how one can analyze a core dump from an application. What are the general guidelines etc. After upgrading ram to 16G from 8G and increasing 3 to 5 processors on a N4000, Oracle 9i core dumps (11i machine). HW upgrade done on friday and since than 5 core dumps have been accumulated. file on one core shows SIGSERV and another SIGABRT. Any hints or reference material I could read up on how to analyze core dumps (possible stack trace calling the kills?). Any help/suggestions appreciated. |
| ||||
| "BB" <ccc@caraudio.com> writes: > Any hints or reference material I could read up on how to analyze core dumps > (possible stack trace calling the kills?). You just load the core and the executable that produced it into the debugger: gdb /path/to/oracle core (gdb) info thread (gdb) info shared (gdb) thread apply all where However, this will likely not make much sense to you. You'll need to get Oracle support/developers involved. And if you do, they'll tell you what further commands to run to get the info *they* need. Cheers, -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. |