Kbase 16413: How to produce a stacktrace from protrace.pid on SCO
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/01/2000 |
|
How to produce a stacktrace from a protrace.pid file on SCO
The following steps are used to create a readable stack trace from
a protrace.pid file produced during a Progress core dump.
1. Translate the system calls from the executable.
nm -xvp $DLC/bin/_progres > temp.out
2. Format the file.
cat temp.out | sed -e '/^[ ^I]/d'| sort -n | awk '{ print $1 " " $3
}' > temp.done
3. Use vi to remove the first 3 comments in the protrace.pid file.
PROGRESS stack trace as of Tue Oct 22 12:25:13 1996
Command line arguments are
/usr/dlc7c/bin/_progres -pf /u/Rona/Bin/Vardef/params.m.pf
4. Produce the stack trace from the protrace.pid file.
$DLC/bin/trc temp.done protrace.12459 > stack.12459
5. The stack trace file (stack.12459) will be used by Technical
Support to isolate the cause of the problem. Both the original
protrace.pid and the converted stack file should be sent to
Technical Support for review.
Notes:
1.) The file protrace.pid does not actually have the extension ".pid".
The extension is actually the process ID (PID) of the process
that recieved the memory violation. For instance, if the process
ID was 823, then the file would be named protrace.823.
2.) The nm program may not be available on all SCO systems. It is
part of the Development toolkit which is licensed separately
from SCO.
3.) The executable may not always be _progres. Sometimes, a core
dump may be produced by a server or background process. In this
case, the appropriate executable (i.e. _mprosrv, _mprshut) should
be subsituted in place of _progres.
Progress Software Technical Support Note # 16413