AIX

Hi All ,

i found two core files on aix customer machine due to two pro-c executables . we dont have any debugger like dbx . even i captured the log reports reg the core dumps .. i pasted the details here belo3w .please help me out h ow to resolve the issue :-( .... THANKS IN ADVANCE ...

core_dump 1 : Executable name : ProcessIse
*************************************
iprsdev@ai135$ file ProcessIse
ProcessIse: 64-bit XCOFF executable or object module not stripped
iprsdev@ai135$ what ProcessIse
ProcessIse:
61 1.15 src/bos/usr/ccs/lib/libc/__threads_init.c, libcthrd, bos53H, h2006_10B1 3/5/06 16:44:5

Log Report :
********
---------------------------------------------------------------------------
LABEL: CORE_DUMP
IDENTIFIER: 40E9A4E1

Date/Time: Mon Aug 11 13:10:56 EDT 2008
Sequence Number: 40431
Machine Id: 00016EBCD700
Node Id: ai135
Class: S
Type: PERM
Resource Name: SYSPROC

Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED

Probable Causes
SOFTWARE PROGRAM

User Causes
USER GENERATED SIGNAL

Recommended Actions
CORRECT THEN RETRY

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
SIGNAL NUMBER
11
USER'S PROCESS ID:
1171650
FILE SYSTEM SERIAL NUMBER
27
INODE NUMBER
704
PROCESSOR ID
0
CORE FILE NAME
/iprs/bin/core
PROGRAM NAME
ProcessIse
STACK EXECUTION DISABLED
0
COME FROM ADDRESS REGISTER
??
ADDITIONAL INFORMATION
fgets B0
fgets 8C
18C
interact_ 28
540
ÿ-91-øa 118
??
__start 9C
Unable to generate symptom string.
Bad return from kprobe().
*******************************************************
core_dump 2 : Executable name : testsend
***********************************
iprsdev@ai135$ file testsend
testsend: executable (RISC System/6000) or object module not stripped

iprsdev@ai135$ what testsend
testsend: 23 1.5 src/bos/usr/ccs/lib/libpthreads/init.c, libpth, bos53H, h2006_10B1 3/5/06 21:33:24
61 1.15 src/bos/usr/ccs/lib/libc/__threads_init.c, libcthrd, bos53H, h2006_10B1 3/5/06 16:44:58

Log Report:
*********
LABEL: CORE_DUMP
IDENTIFIER: 40E9A4E1

Date/Time: Mon Aug 11 19:11:01 EDT 2008
Sequence Number: 40432
Machine Id: 00016EBCD700
Node Id: ai135
Class: S
Type: PERM
Resource Name: SYSPROC

Description
SOFTWARE PROGRAM ABNORMALLY TERMINATED

Probable Causes
SOFTWARE PROGRAM

User Causes
USER GENERATED SIGNAL

Recommended Actions
CORRECT THEN RETRY

Failure Causes
SOFTWARE PROGRAM

Recommended Actions
RERUN THE APPLICATION PROGRAM
IF PROBLEM PERSISTS THEN DO THE FOLLOWING
CONTACT APPROPRIATE SERVICE REPRESENTATIVE

Detail Data
SIGNAL NUMBER
11
USER'S PROCESS ID:
2289756
FILE SYSTEM SERIAL NUMBER
27
INODE NUMBER
193
PROCESSOR ID
2
CORE FILE NAME
/iprs/persistent/run/core
PROGRAM NAME
testsend
STACK EXECUTION DISABLED
0
COME FROM ADDRESS REGISTER
??
ADDITIONAL INFORMATION
fprintf 4C
??
??
??
__start 9C

Symptom Data
REPORTABLE
1
INTERNAL ERROR
0
SYMPTOM CODE
PCSS/SPI2 FLDS/testsend SIG/11 FLDS/fprintf VALU/4c FLDS/__start

**********************************************************

Please advice me , how to resolve the problem ...

Some more information about ProcessIse core_dump from dbx :
***********************************************
(/usr/bin/dbx) where
ustart() at 0x9fffffff0000240
(/usr/bin/dbx) step
stopped in IprsIseInterface::execute(int,char**,IprsIseInterface*(*)(const char*)) at line 101 in file "" ($t1)
could not read "ProcessIseInterface.C"
(/usr/bin/dbx) func
IprsIseInterface::execute(int,char**,IprsIseInterface*(*)(const char*))

********************************************************

dbx is part of the AIX operating system and thus could be used without additional costs (fileset bos.adt.debug). Any chance to have it installed?

To Shockneck ...

if we have dbx , is it possible to debug the executable with out changing the source code ? .. because i dont have much idea abt core_dump n dbx .. :-( is dbx used to identify the problem or resolving the problem ?

Dbx is mainly for identifying problems in your code by running it line by line but it can also be used to change variables. However, AFAIK the program you want to debug needs to be compiled with the -q option if using dbx should make much sense. You can use it without but the possibilities will be limited then. Have a look in the dbx manpage for a start.

lemme try ... we transfered the core file to another machine which having dbx n ran some commands ... the output is pasted below ...

(/usr/bin/dbx) where
ustart() at 0x9fffffff0000240
(/usr/bin/dbx) step
stopped in IprsIseInterface::execute(int,char**,IprsIseInterface*(*)(const char*)) at line 101 in file "" ($t1)
could not read "ProcessIseInterface.C"
(/usr/bin/dbx) func
IprsIseInterface::execute(int,char**,IprsIseInterface*(*)(const char*))

***************************************************************
???? anyone can get any idea about the problem in the code ?