Kbase 15731: stack trace : can't unwind -- no entry
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
stack trace : can't unwind -- no entry
=====================================================================
INTRODUCTION
There are still many customers who tell us that, given a core file,
they cannot get a stack trace. Typically, the stacktrace file
contains the line " can't unwind -- no entry "
=====================================================================
CORRECTIVE MEASURES:
This problem has been fixed on the platforms listed below, as of
the patch levels also listed. With these patch levels there will
still be a file named core in the working directory, but additionally
there will be a file named protrace.nnnn, where nnnn is the pid of
the executable that produced the core file. The EXCEPTION to this is
on Intel based platforms (386, 486 and pentium) where there is no
symbol table resident in memory for the executable. On these plat-
forms, there will still be produced a file named protrace.nnnn with
lines that look like:
9d7c0 (x7ffff3a8, xffffffff, x6c682, xa01bf)
9d6bc (x7ffff400, x61b6, x2, x2)
5ddc (x2, x2, x7ffff494, xab19d)
Now do a more protrace.nnnn to get the <pathname> of the executable
and then do tracecnv <pathname> protrace.nnnn > trace.txt
The trace.txt will then contain lines that look like:
9D7C0 ---> uttrace (x7ffff3a8, xffffffff, x6c682, xa01bf)
9D6BC ---> utcore (x7ffff400, x61b6, x2, x2)
5DDC ---> drexit (x2, x2, x7ffff494, xab19d)
NOTE: If tracecnv is not in the $DLC/bin directory, try $DLC
=====================================================================
WHERE FIXED:
DG/UX V.4 7.3C04
HP825 " 6.3F10
IBM RS6K "
SCO UNIX " 6.3F07
SOLARIS 2.3 "
SUN SPARC "
UNIX486 V.4 "
MIPS V.4 7.3C07 6.3F04
SEQ. PTX 7.3C06 6.3F03
SUN 4X4 6.3F03
Progress Software Technical Support Note # 15731