analyse core file using pmap and pstack

UNIX Solaris
1

Dear All,
I am new to this forum. This is my first.
I am facing customer issue. Customer has got core file while running the server.
He had sent core file and details from pstack, pmap and pldd commands.
I have to debug this application, please help me to fix this issue.

I am using sparc 10 solaris machine. Code is not given.

Any help is appreciated.

Thanks
Kiran

2

It would be probably tricky for you to debug the application without having its source code (assuming it is what you mean with "code is not given"). It would be even trickier for any of us to help if you don't post the pstack/pmap/pldd output.

3

If the application was compiled with debug symbols you can try to find out where it crashed ( use gdb ) .
You will need the core file AND the application ( binary + so files , if any ) .
You can't really debug in gdb without source , but sometimes you can get very valuable info ( function names , arguments , instruction pointer , registers , etc )

4

Thanks for the reply.
They have given core file and binary + so files.

By using dbx I got the following output.

(dbx) threads
       t@74  a l@74   ?()   LWP suspended in  __pollsys()
     t@75  a l@75   ?()   LWP suspended in  __pollsys()
o   t@145  a l@145   NdbThread_set_shm_sigmask()   signal SIGABRT in  __lwp_kill()
    t@152  a l@152   ?()   sleep on 0xae3b88  in  __lwp_park()



(dbx) thread t@145
t@145 (l@145) stopped in __lwp_kill at 0xfeb4c5f8
0xfeb4c5f8: __lwp_kill+0x0008:  bcc,a,pt  %icc,__lwp_kill+0x18  ! 0xfeb4c608
(dbx) where
current thread: t@145
=>[1] __lwp_kill(0x0, 0x6, 0xf87a4444, 0xeeb60, 0xfebb33d8, 0x0), at 0xfeb4c5f8
  [2] raise(0x6, 0x0, 0xfebb5258, 0xfed30b00, 0xffffffff, 0x6), at 0xfeae5a5c
  [3] abort(0x0, 0x1, 0xf87a4444, 0xeeb60, 0xfebb33d8, 0x0), at 0xfeac194c
  [4] free(0x129a030, 0x129b2d0, 0x0, 0x40, 0x1, 0x40000000), at 0xfed30b00
  [5] NdbThread_Destroy(0xcfe080, 0xfda97e6c, 0xdcec, 0xdcec, 0xdcec, 0xdcec), at 0xf87a4444
  [6] TransporterRegistry::stop_clients(0xcfe068, 0x1, 0x1109d7c, 0xffffffff, 0x1, 0x1109d6c), at 0xf87dac70
  [7] TransporterFacade::threadMainSend(0x10fc078, 0x1, 0xdcec, 0xdcec, 0xdcec, 0xdcec), at 0xf87b5e00
  [8] runSendRequest_C(0x10fc078, 0xfda97f90, 0x0, 0xfc6bfa00, 0xfebb03a8, 0x1), at 0xf87b5d08
  [9] 0xf87a4260(0xcfe680, 0x0, 0x0, 0x0, 0xf87b5d04, 0x1), at 0xf87a4260
(dbx)

I think was it using some third party libraries. How to find the function calls, return value etc.

5

I am sorry , which part of the debugger output looks unfamiliar to you ?
You start with [9] and go down through calls .