Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Analysing a core dump.
Operating Systems Solaris Analysing a core dump. Post 302269269 by efunds on Wednesday 17th of December 2008 08:31:11 AM
Old 12-17-2008
Analysing a core dump.
Friends

I was trying to analyse a core dump using pstack command in Sol5.9(Sparc)
The output is as below.
[!]root: pstack core_mumux211_istauth_220_108_1229517198_21922
core 'core_mumux211_istauth_220_108_1229517198_21922' of 21922: istauth
fe1afbb8 ttcdrv (c10e0, c1db4, 30ad8, bc950, 0, 0) + 124
fe06a958 nioqwa (0, c8bb8, fe1afa94, c10e0, 30b00, 0) + 50
fdea0cac upirtrc (30ad8, 8, bc950, 0, 0, 1) + 6b4
fdea052c upirtr (30ad8, 8, ffbf2898, c0fc8, 0, 0) + a8
fde86618 upicls (30ad8, 5, 0, 0, 0, 2000) + 348
fde63068 ociclo (c9fa0, 10, 0, 0, c9fa0, ac) + 44
ff25d9ac oracle_free_stmt (c9f70, c9f70, 0, 0, 0, 0) + 44
ff250618 DBMFreeStmt (c9f70, 1, 0, 0, 0, 0) + b8
ff25c834 free_stmt_desc (128064, 0, 0, 0, 0, 0) + 4c
ff256a10 do_dbm_close (0, 0, 0, 0, 0, 0) + 68
ff256c54 dbm_close_all (55a2, 50f6, ffbf2b90, 0, ffbf2b88, feebc000) + 6c
000114d8 __1cHCleanup6F_i_ (23, b, ffbf2b68, 0, 0, 0) + 28
0001121c pexit (b, 0, 0, 0, 0, 0) + 1c
ff1c060c catch_sig (b, 0, ffbf2cd0, feebc000, 0, 0) + 64
fee9f834 sigacthandler (b, 0, ffbf2cd0, 0, 6937e8, 10002da3) + 28
--- called from signal handler with signal 11 (SIGSEGV) ---
fe1afbb8 ttcdrv (c10e0, c1db4, 30ad8, bc950, 0, 0) + 124
fe06a958 nioqwa (0, c8bb8, fe1afa94, c10e0, 30b00, 0) + 50
fdea0cac upirtrc (30ad8, 8, bc950, 0, 0, 1) + 6b4
fdea052c upirtr (30ad8, 8, ffbf7db8, c0fc8, 0, 0) + a8
fde86618 upicls (30ad8, 5, 0, 0, 0, 2000) + 348
fde63068 ociclo (c9fa0, 10, ff3f0230, 23dac, c9fa0, ac) + 44
ff25d9ac oracle_free_stmt (c9f70, c9f70, 0, ff3f07c4, ff234fa4, f0000000) + 44
ff250618 DBMFreeStmt (c9f70, 1, 3, ff3f3dd8, 10, ffbf7f5c) + b8
ff25c834 free_stmt_desc (128064, 10, 10ef4, ff241ab8, 5, 0) + 4c
ff256a10 do_dbm_close (0, 0, 0, 0, 0, 0) + 68
ff256c54 dbm_close_all (55a2, 50f6, ffbf80b0, 0, ffbf80a8, feebc000) + 6c
000114d8 __1cHCleanup6F_i_ (23, f, ffbf8088, 0, 0, 0) + 28
0001121c pexit (f, 0, 0, 0, 0, 0) + 1c
ff1c060c catch_sig (f, 0, ffbf81f0, feebc000, 0, 0) + 64
fee9f834 sigacthandler (f, 0, ffbf81f0, d9696, d57cc, 0) + 28
--- called from signal handler with signal 15 (SIGTERM) ---
fee9f4ac _read (d67f8, d6dd0, d5a28, d5fde, d5a94, 0) + c
fe1588dc ntprd (fe046980, d5fde, d5a94, 0, 0, 97b234) + 70
fe04a5a0 nsprecv (d5630, 800, c8d7c, d5fde, d5928, 0) + 150
fe04e284 nsrdr (d5630, c8d7c, d5810, 6000, 0, 0) + 134
fe02e20c nsdo (ce758, 55, d8e80, c8dc0, ffbf924f, c8d7c) + 11e4
fe02cf40 nsbrecv (c8c60, c8d7c, ffbf924f, 0, 3, 3) + 20
fe062754 nioqrc (c8bb8, d8ec2, c10ef, 1, 0, 30b7c) + 4e0
fe1afe88 ttcdrv (c10e0, 3, 30ad8, bc950, 0, 0) + 3f4
fe06a958 nioqwa (0, c8bb8, fe1afa94, c10e0, 30b00, 0) + 50
fdea0cac upirtrc (30ad8, 4, bc950, 0, 0, 0) + 6b4
fde9d6f0 upiex0 (30ad8, 0, 20, 1572b8, 1, c10e0) + 598
fde6382c ociexe (13a5d8, 4, 1, fde642f8, 13a5d8, ac) + 5c
ff25f258 oracle_execute (13a5a8, ff27a380, fffffffc, ff27bd6f, 45, b67) + 8f0
ff25f5cc oracle_exec_direct (13a5a8, ff27a380, 25be, 29, 4, 0) + 74
ff251018 DBMExecDirect (13a5a8, ff27a380, ff27a380, 2710, ff399a64, ffbff26d) + 140
ff259af8 do_selectfd (8, ff399a64, 1, 0, 0, 0) + 298
ff259e44 dbm_selectfd (8, ff399a64, 1, 0, feebf82d, 0) + 9c
ff325944 __1cKist_select6Fipkc_i_ (10, ff399a64, ffbff410, 1, 7fffff85, ff26c7de) + cc
ff325808 __1cPist_fetchrecord6Fipkc_i_ (10, ff399a64, ff399ade, 13d262, 81010100, ff00) + 38
ff325774 __1cOist_readrecord6FipcpnKistauthmsg__i_ (10, ff399a64, 25f88, 2639a, 13d262, 12d2f4) + 3c
ff334664 __1cQValidateRelation6FpnKistauthmsg__i_ (13d262, ffbff524, 2642c, 0, 3000, ffbff498) + 154
ff317b04 __1cPValidateAccount6FpnKistauthmsg__i_ (25f88, 29710, 0, feebc000, 0, 0) + 644
ff32469c __1cNist_authorize6FpnKistauthmsg__i_ (25f88, ff207629, ff21b2d4, 7efefeff, 81010100, ff00) + 2f4
ff3242dc __1cList_finauth6FpnKistauthmsg__i_ (25f88, 12, 3, ff21b2d4, 2af8, 2bf) + 184
ff33fa80 __1cKProcessShc6FpnKistauthmsg__i_ (2bf, ffbff6a2, 0, 0, 4, 0) + 128
0001164c __1cHProcess6F_i_ (0, 2, 28, ff21b2d4, 22378, 14) + 144
000111b8 main (1, ffbff814, ffbff81c, 21c00, 0, 0) + 68
00011128 _start (0, 0, 0, 0, 0, 0) + 108
@ /users/d08083


Can anyone help me in understanding this. Any links,Any suggestions,Any Guidance is greatly appreciated.

Thanks
HG
efunds
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

help, what is the difference between core dump and panic dump?

help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies

2. UNIX for Dummies Questions & Answers

core dump

I've got a core dump in my weblogic home directory, which i have tried to debug by initiating savecore from /etc/init.d/savecore start but savecore failed to create the two files, that is vmcore.n and vmunix.n. savecore is enable on my server to save vmcore and vmunix in /var/crash/hostname 1)... (4 Replies)
Discussion started by: hassan2
4 Replies

3. Programming

about core dump

MY friends: my program under sco unix have a problem? it create a core dump file on the path when execute program , but i can't find the error of the C program ,i don't know how to see the error about my program use core, please help me or give me some suggest and what tools can use... (1 Reply)
Discussion started by: zhaohaizhou
1 Replies

4. UNIX for Advanced & Expert Users

core dump

Hi All, i am new to this forum.i want detail of reading the core file and trace the problem because of what the program get crashed.please help me.if any body knows any website or tutoril plese let me know. sudhir (6 Replies)
Discussion started by: sudhir patnaik
6 Replies

5. UNIX for Dummies Questions & Answers

Core dump in HP-UX..

Hi All I am new for this forum. I have a core file by using gdb and bt cmd I got the function name but I want to the exact cause of the core dump because of I can not reproduse the binary so if any one know the cmd plz plz plz let me know. (0 Replies)
Discussion started by: gyanusoni
0 Replies

6. UNIX for Advanced & Expert Users

Core Dump

Hello all, Iam new to unix while executing java program which finely working in windows know iam testing with unix ,but in unix while executing iam getting core dump, my application is in client server environment and it is menu drivrn application on clicking options no problem but after some time... (1 Reply)
Discussion started by: vinp
1 Replies

7. HP-UX

Query: Analysing the Core file

Hi, Is there any way to find the mode of the binary file (debug or release) by analyzing the core file generated by that binary on the HPUX11i Platform? (5 Replies)
Discussion started by: Prajakta
5 Replies

8. Programming

core dump

how to view core dumped file using gdb and how to extract information from the coredumped file.can we get similar information from the other utilites like strace or ptrace. (2 Replies)
Discussion started by: Manabhanjan
2 Replies

9. AIX

Core dump

Hi , I want to read core dump file on AIX5.3. While i am trying to use following commands, i am getting only few lines of information. ux201p3:e46123> dbx capsWrkstnMgr core Type 'help' for help. reading symbolic information ... Segmentation fault in malloc_common.extend_brk at... (1 Reply)
Discussion started by: rps
1 Replies

10. Solaris

core dump

Hi guys, just want to know which core file pattern is best to set for core dumps: 1) per-process file name pattern or 2) global file name pattern. I will really appreciate an explanation why the chosen one is better. Thanks a lot guys. (2 Replies)
Discussion started by: cjashu
2 Replies

LEARN ABOUT MOJAVE

gcore

gcore(1)						    BSD General Commands Manual 						  gcore(1)

NAME

     gcore -- get core images of running processes

SYNOPSIS

     gcore [-s] [-v] [-b size] [-o path | -c pathformat] pid

DESCRIPTION

     The gcore program creates a core file image of the process specified by pid.  The resulting core file can be used with a debugger, e.g.
     lldb(1), to examine the state of the process.

     The following options are available:

     -s 	 Suspend the process while the core file is captured.

     -v 	 Report progress on the dump as it proceeds.

     -b size	 Limit the size of the core file to size MiBytes.

     The following options control the name of the core file:

     -o path
	   Write the core file to path.

     -c pathformat
	   Write the core file to pathformat.  The pathformat string is treated as a pathname that may contain various special characters which
	   cause the interpolation of strings representing specific attributes of the process into the name.

	   Each special character is introduced by the % character.  The format characters and their meanings are:

	   N	       The name of the program being dumped, as reported by ps(1).

	   U	       The uid of the process being dumped, converted to a string.

	   P	       The pid of the process being dumped, converted to a string.

	   T	       The time when the core file was taken, converted to ISO 8601 format.

	   %	       Output a percent character.

     The default file name used by gcore is %N-%P-%T.  By default, the core file will be written to a directory whose name is determined from the
     kern.corefile MIB.  This can be printed or modified using sysctl(8).

     The directory where the core file is to be written must be accessible to the owner of the target process.

     gcore will not overwrite an existing file, nor will it create missing directories in the path.

EXIT_STATUS
     The gcore utility exits 0 on success, and >0 if an error occurs.

FILES

     /cores/%N-%P-%T	   default pathname for the corefile.

BUGS

     With the -b flag, gcore writes out as much data as it can up to the specified limit, even if that results in an incomplete core image.  Such
     a partial core dump may confuse subsequent programs that attempt to parse the contents of such files.

SEE ALSO

     lldb(1), core(5), Mach-O(5), sysctl(8), sudo(8).

Darwin								   May 31, 2019 							    Darwin
All times are GMT -4. The time now is 02:58 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy