adb and dbx gives different stack backtraces

adb and dbx gives different stack backtraces

Post by Denis Ustimen » Thu, 24 Jun 2004 06:11:17



Hi there!

Does anybody know why sometimes dbx and adb gives different backtraces
on the same core file?

--
Best regards
Denis

 
 
 

1. dbx: Can dbx read core files from different machines?

dbx barfs with:

core file header read successfully
dbx: core file read error: address 0xef7fbf78 not available
dbx: panic: Proc::get_rtld_stuff(): could not initialize rtld_db

when trying to load a core file from another machine.

Surely, DBX can read cores generated on a different arch/memory
config!

And yes, I have patched dbx with the latest.

Any ideas, pointers?

Steve

2. X Install Problem: "X startup failed, falling back to text mode" (Red Hat 6.2)

3. call stack backtrace from a C program

4. GNU Window manager shortcut standard proposition

5. Stack backtrace from signal handler

6. 504 UUCP dials OK, SCOPPP receives garbage.

7. Stack Backtrace for Solaris 2.3/SunPro C 2.0

8. Banyan and Linux

9. How to backtrace stack frames?

10. Seeking stack backtrace function

11. call stack backtrace from a C program (Solaris)

12. How to backtrace stack frames?

13. Interpreting the results from backtrace()/ backtrace() usability