[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::c_plus_plus

Title:C++
Notice:Read 1.* and use keywords (e.g. SHOW KEY/FULL KIT_CXX_VAX_VMS)
Moderator:DECCXX::AMARTIN
Created:Fri Nov 06 1987
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3604
Total number of notes:18242

3551.0. "ladebug 4.0-35 stack traces" by NNTPD::"[email protected]" (Bill Reese) Wed Apr 23 1997 14:26

I've been playing around with the 5.6-003 field test 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
version.


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.

Bill Reese

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
3551.1Ladebug conferenceDECC::SULLIVANJeff SullivanWed Apr 23 1997 14:308
You will probably get a better response in the Ladebug notes conference.
I'm sure they will be interested in your findings.
See pointer above.

Thanks for reporting the problems.

-Jeff

3551.2repostedNNTPD::"[email protected]"Bill ReeseFri Apr 25 1997 10:506
Jeff,
     Thanks for the tip; I've reposted the note in the ladebug conference,
along with another trace or two.
Bill

[Posted by WWW Notes gateway]