468,765 Members | 1,253 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,765 developers. It's quick & easy.

cannot run dbx to debug a core...

I got a core from my client but i am not able to find out where it
crashed. I got the following:

From my experience, when i got lots of warning which complains about
the path mismatch.. I can use "pathmap" to tell dbx the new path of
the libraries and then use "where" to find out where it crashed.
however, this time, the DBX itself crashed. I can no way to use
pathmap. Can any guru kindly tell me what i can do to debug the core?
How can I check if it is a complete core?
Thanks.

dbxenv suppress_startup_message 6.2
Reading GL_CliConnMgr
core file header read successfully
Reading ld.so.1
dbx: core file read error: address 0xff3e6000 not available
Reading libpthread.so.1
Reading libresolv.so.2
dbx: warning: The corefile has a different ELF checksum for
/usr/lib/libresolv.so.2
checksums are: file: 0x3870 core: 0xbd80
See `help core mismatch' for more details.
Reading libsocket.so.1
Reading libnsl.so.1
dbx: warning: The corefile has a different ELF checksum for
/usr/lib/libnsl.so.1
checksums are: file: 0xf151 core: 0x0bff
See `help core mismatch' for more details.
dbx: can't stat /export/home/oracle/product/9.2.0/lib32/libclntsh.so.9.0
-- No such file or directory
Reading libclntsh.so.9.0
dbx: warning: Couldn't open file:
/export/home/oracle/product/9.2.0/lib32/libclntsh.so.9.0 (No such file
or directory)
dbx: internal error: Can't read
/export/home/oracle/product/9.2.0/lib32/libclntsh.so.9.0

Reading libCrun.so.1
Reading libm.so.1
Reading libw.so.1
Reading libthread.so.1
Reading libc.so.1
dbx: warning: The corefile has a different ELF checksum for
/usr/lib/libc.so.1
checksums are: file: 0x43dc core: 0x97ae
See `help core mismatch' for more details.
Reading libdl.so.1
Reading libmp.so.2
dbx: can't stat /export/home/oracle/product/9.2.0/lib32/libwtc9.so --
No such file or directory
Reading libwtc9.so
dbx: warning: Couldn't open file:
/export/home/oracle/product/9.2.0/lib32/libwtc9.so (No such file or
directory)
dbx: internal error: Can't read
/export/home/oracle/product/9.2.0/lib32/libwtc9.so

Reading libgen.so.1
Reading libsched.so.1
Reading libaio.so.1
Reading librt.so.1
dbx: warning: The corefile has a different ELF checksum for
/usr/lib/librt.so.1
checksums are: file: 0xeb91 core: 0xea15
See `help core mismatch' for more details.
Reading libc_psr.so.1
detected a multithreaded program
t@4 (l@3) terminated by signal ABRT (Abort)

dbx: internal error: signal SIGSEGV (no mapping at the fault address)
dbx's coredump will appear in /tmp
Abort (core dumped)
Jul 19 '05 #1
1 5159
Martin wrote:
I got a core from my client but i am not able to find out where it
crashed. I got the following:

From my experience, when i got lots of warning which complains about
the path mismatch.. I can use "pathmap" to tell dbx the new path of
the libraries and then use "where" to find out where it crashed.
however, this time, the DBX itself crashed. I can no way to use
pathmap. Can any guru kindly tell me what i can do to debug the core?
How can I check if it is a complete core?
Thanks.


Sounds like your issue is with a platform or the debugging
utility, and not with the language. Have you tried posting
to newsgroups about the platform or debugger?

Read the FAQ and welcome.txt below.

--
Thomas Matthews

C++ newsgroup welcome message:
http://www.slack.net/~shiva/welcome.txt
C++ Faq: http://www.parashift.com/c++-faq-lite
C Faq: http://www.eskimo.com/~scs/c-faq/top.html
alt.comp.lang.learn.c-c++ faq:
http://www.raos.demon.uk/acllc-c++/faq.html
Other sites:
http://www.josuttis.com -- C++ STL Library book

Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

1 post views Thread by Ryan | last post: by
9 posts views Thread by Maksim Kasimov | last post: by
1 post views Thread by CARIGAR | last post: by
reply views Thread by Marin | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.