core file tracing

[A Pandey]

Hi,

I got the following output from #what core




core:

NSPR 4.1.2 Thu Jun 21 15:51:16 PDT 2001

NSPR 4.1.2 Thu Jun 21 15:51:13 PDT 2001

NSPR 4.1.2 Thu Jun 21 15:51:10 PDT 2001

STREAMS: Revision: B.11.00 $Date: 2003/01/02 15:00:00 $

Pthread Interfaces
libpthread HP-UX (Release B.11.00): Thu Jul 5 15:26:27 PDT 2001

LWP (LightWeightProcess) Interfaces
liblwp HP-UX (Release B.11.00): Fri Oct 24 05:02:08 PDT 1997

HP-UX libm shared PA1.1 C Math Library 20000331 (201031) UX11.01

HP-UX libisamstub.sl 19991217 (135120) B3907DB/B3909DB B.11.01.11

fs_amod.s $Revision: 1.9.1.1 $
libcl.sl version B.11.01.18 - Jan 3 2003

$ PATCH/11.00:PHCO_29633 Sep 26 2003 06:07:40$

SMART_BIND

92453-07 dld dld dld.sl B.11.37 030909

[Bill Hassell]

This is a list of module identifiers inside the program. It doesn't give you any information about the name of the program itself or the reason for the core dump. Use the file command as in:

file core

[A Pandey]

i got:

core: core file from 'uxwdog' - received SIGABRT


are there any other commands i could use?

[Fred Ruffet]

Not that I know, but this already indicates you which program generated the core and why.

uxwdog seems to be an iPlanet process. Maybe you should search for iPlanet reports in syslog at the same time the core file was generated.

Regards,

Fred

[A Pandey]

i got:


Nov 17 09:09:00 servername uxwdog[4051]: error communicating with server (Broken pipe)



I have replaced our server name with servername above just for security issues.


Also we do run iPlanet on this server, but I don't have much idea of uxwdog?

thank you for all your help.

ap.

[Fred Ruffet · Accepted solution]

From its name I would say it is a watchdog process (a process to monitor and report on others).

I can't go further for now as long as I don't use iPlanet.

Regards,

Fred

[A. Clay Stephenson]

Now that you have used file to identify the executable, you can use a debugger to get a stack trace. That data are extremely valuable to the developer or vendor. If you have gdb on your box use it otherwise use adb.

Gdb will generate a stack trace automatically
simply by:
cd to directory with core
gdb /full/path/name/to/exe core

Man gdb and/or adb for details. The idea of a stack trace is that it indicates the chain of function calls that lead to the program crash.

[A Pandey]

thnks to everyone...

i got this output:

can't unwind -- no_entry

the mystery deepens!!!

[Bill Hassell]

From Google, uxwdog is part of Netscape Enterprise Server and the broken pipe message appears in several items in Google. However, since you don't have the source code to fix the program, you'll have to go to Netscape for help, probably a patch or update. Note that the exact message:

uxwdog error communicating with server (Broken Pipe

is associated with either Netbackup or iPlanet in several articles found in Google, but no simple answer.