Conference turris::decladebug

951.0. "4.0-37 broken for kernel crash dumps" by RDGENG::HAQUE (Shaheed R. Haque, 830-3531, reo2-f/b3) Fri May 09 1997 05:26

ladebug V4.0-36 and V4.0-37
Digital UNIX V3.2C and V4.0B

The above versions of ladebug fail miserably in the same way when trying to do
any kernel crash dump analysis. This is what happens with -37 on V3.2C:

moore# ladebug -k vmunix.0 vmcore.0
Welcome to the Ladebug Debugger Version 4.0-37
------------------
object file name: vmunix.0
core file name: vmcore.0
Assertion failed: aProgram src/libsrc/ladebug/process.C 669
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Diagnostic stack trace ...
0x12419ce8
0x1241821c
0x1241b208
0x124205e4
0x12423de0
0x12422074
0x12391e14
0x12232438
0x12233d84
0x122229d0
0x1221fb44
end of diagnostic stack trace.
Assertion failure
Fatal error: Could not attach to kernel.
moore#

and with -37 on V4.0B:

# ladebug -k vmunix.3 vmcore.3
Welcome to the Ladebug Debugger Version 4.0-37
------------------
object file name: vmunix.3
core file name: vmcore.3
Assertion failed: aProgram src/libsrc/ladebug/process.C 669
This is an unexpected condition and may indicate the presence of a defect.
If you wish to report this, please include the stack trace that follows.
Diagnostic stack trace ...
0x1241ed78
0x1241d2ac
0x124202a8
0x12425794
0x12428f90
0x12427224
0x12396974
0x12236bf8
0x1223863c
0x122270e0
0x1222426c
end of diagnostic stack trace.
Assertion failure
Fatal error: Could not attach to kernel.
#

Note that this all worked just fine in -30, on both OS versions. Maybe its time
to add a few basic kernel crash dump tests to the ladebug regression test suite?
(:-)).

Since I am also using threads and C++, it would be really nice to have a single
debugger that I could use for all my debug jobs...any chance of a quick fix?

	Thanks, Shaheed

I can reproduce the problem here - we will investigate and report the
status.

shamim