Core Dump

[James Elliott_2]

I have an application compiled in ancii C. When i run the application I get a core dump. I then use adb app name core then $c and i recieve the following :
$ adb ouptime core
PA-64 adb ($h help $q quit)
adb>$c
u_ltoa+8C from u_ltoa
u_ltoa() from ulongtos+47
ulongtos() from uPutReg100+0xCB
uPutReg100() from uPutStatus+4B
uPutStatus() from uuprocs+13AB
uuprocs() from uIniProCtx+567
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from ufrmexec+5F
ufrmexec() from urunx+0xA7
urunx() from uIniProCtx+797
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from uIniProCtx+603
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from uIniProCtx+603
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from ufprocs+19F
ufprocs() from UFormManager+1F03
UFormManager() from uResetInstances+23F
uResetInstances() from UProcessNextEvent+153
UProcessNextEvent() from uesrun+93
uesrun() from uIniProCtx+81F
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from ufrmexec+5F
ufrmexec() from urunx+0xA7
urunx() from uIniProCtx+797
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from uIniProCtx+603
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from ufprocs+19F
ufprocs() from UFormManager+1F03
UFormManager() from uResetInstances+23F
uResetInstances() from UProcessNextEvent+153
UProcessNextEvent() from uesrun+93
uesrun() from uIniProCtx+81F
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from ufrmexec+5F
ufrmexec() from urunx+0xA7
urunx() from uIniProCtx+797
uIniProCtx() from uxprocs+5F
uxprocs() from uprocs+4F
uprocs() from uapscreen+23F
uapscreen() from uapscrn+17
uapscrn() from UNIMAIN+91F
UNIMAIN() from UXMAIN+173
UXMAIN() from main+83
main() from floor+7733
floor(
cannot unwind -- no unwind descriptor (3)
adb>
Would like to know if some one could help and could to get the application running with out the core dunp.

[Biswajit Tripathy]

Can you post the exact error before core dump?
(Like "Bus Error", or "Segmentation violation" etc.)

- Biswajit

[A. Clay Stephenson]

You should compile your source with the -g option and use gdb or xdb to debug. If you do this, your stack trace will identify the exact line in the source code.