Conference turris::decladebug

935.0. "ladebug 4.0-35 stack traces" by NNTPD::"[email protected]" (Bill Reese) Fri Apr 25 1997 10:48

I've been playing around with the 5.6-003 field test C++ compiler and ladebug
4.0-35 on Digital Unix 4.0a.  I've come across a couple of debugger deaths I
thought you might want to see.  All of these are from the command line
debugger.


------------------------------------------------------------------------------
---------

This first one I didn't have quite enough swap space (obviously).

(ladebug) rerun
Unable to obtain requested swap space
fork failed: Operation would block

Assertion failed: thread src/dbx/state.C 419
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 ...
0x12238998
0x1223c59c
0x1224b398
0x12215f24
0x12217f9c
0x12217d80
0x12214d7c
end of diagnostic stack trace.
Fatal Error: unable to exit cleanly.  Aborting...


------------------------------------------------------------------------------
---------

After adding more swap and tracing through a few things, I got this one.  I've
included an initial error that I ignored, which may have caused the eventual
dump.


(ladebug) rerun
Unable to create a thread list using decthreads.
Unable to switch to decthreads mode.
[1] stopped at [DummyForAlphabetFunctions::DummyForAlphabetFunctions(void):25
0x
...
a few continue commands and list commands
...
(ladebug) p alphabet_
Error: More than one static declaration of alphabet_ in the same scope
Info: Compiler may have treated static locals as globals in the debug sym
table
Info: Ignoring declarations due to a name clash
Error: no value for alphabet_
(ladebug) ni
Assertion failed: 0 != thread src/libsrc/ladebug/controlevent.C 504
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 ...
0x1238e82c
0x12416bb8
0x124171d8
0x12407d1c
0x124120e4
0x12382764
0x1225a8f8
0x1225b82c
0x12223424
0x12227970
0x12217bac
0x12214d7c
end of diagnostic stack trace.

This one left me still in the debugger.

------------------------------------------------------------------------------
---------

Here's another.  I had yet to run anything; I was just getting some
breakpoints set.

(ladebug) stop in AlphabetRegistry<Numeric_e>::Alphabet
[#1: stop in Array__T9RWCString Alphabet(void) ]
(ladebug) stop in AlphabetRegistry<Numeric_e>::AcceptableFor
AlphabetRegistry<Numeric_e>::AcceptableFor has no valid breakpoint address
Warning: Breakpoint not set
(ladebug) stop in AlphabetRegistry<Numeric_e>::AlphabetFor
Assertion failed: s != NULL src/libsrc/ladebug/strdup.C 44
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 ...
0x1240db64
0x124539a4
0x124549ac
0x1244fe28
0x1244f8d4
0x1244ef00
0x1244dc48
0x12581df4
0x12566698
0x123a9bd8
0x123a9f6c
0x123ad7dc
0x12493630
0x124ccf14
0x124d18cc
0x12244f50
0x122431bc
0x12223424
0x12227970
0x12217bac
0x12214d7c
end of diagnostic stack trace.
(ladebug) 

------------------------------------------------------------------------------
---------

And another...

% ladebug primitives_test
Welcome to the Ladebug Debugger Version 4.0-35
------------------ 
object file name: primitives_test 
Reading symbolic information ...done
Directory search path for source files:
 . .. ../../primitive ../../basic
(ladebug) stop in AlphabetRegistry<Numeric_e>::addCanonicalMapping
[#1: stop in void AlphabetRegistry<Numeric_e>::addCanonicalMapping(string&,
Numeric_e) ]
(ladebug) stop in AlphabetRegistry<Numeric_e>::AlphabetFor

Ladebug Debugger Version 4.0-35 caught signal "Segmentation fault" (11).
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 ...
0x12493610
0x124ccf14
0x124d18cc
0x12244f50
0x122431bc
0x12223424
0x12227970
0x12217bac
0x12214d7c
end of diagnostic stack trace.
Fatal error: Segmentation fault



Bill Reese

[Posted by WWW Notes gateway]