Conference turris::decladebug

957.0. "ladebug 4.0-37 asertion failure in threadDebugInterface.C" by PEACHS::LAMPERT (Pat Lampert, UNIX Applications Support, 343-1050) Tue May 20 1997 11:18

c++ 5.5
ladebug 4.0-37
unix 4.0b

A major customer (Loral Aerosys) is having problems with
dxladebug. The program they are attempting to debug is
quite large and uses RogueWave libraries. So they have
not been able to supply a reproducer. 

We updated the customer to 4.0-37 and also tuned their
system for more threads and a larger stack, but the ladebug
is still failing. Here is what they sent me. (typed in
from a fax)...


object file name: ExcuteSceduleMain
reading symbolic information ...done
Setting initial break point in routine "ExecuteScheduleMain.cxx" `main(int, char **)
Assertion faile: tebAddr src/libsrc/ladebug/threadDebugInterface.C 587
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 ...
0x12531078
0x125308e4
0x1241f8f0
0x123a1c54
0x123d2810
0x1241dc54
0x12427f44
0x12395764
0x12260940
0x12232af4
0x122370e0
0x1222712c
0x1222426c
end of diagnostic stack trace.
Unable to create a thread list using decthreads.
Unable to switch to decthreads mode.
[1] when [int main(int, char **):51 0x120178a0c]
[1] stopped at [int main(int, char **):51 0x120178a0c]
	5)	if(veEvent.EventGenerateInit() != cSUCCESS)
(ladebug)


I cant help, based in the nature of the message "unable
to create thread list", thinking that there is some sort
of tuning thing going on, but I dont see where it is.

Pat

Thanks - we will try to duplicate this.  It is very unlikely we will get the
fix into BL38 (unless you are just lucky) - but it might well be worth
asking them to try C++ 5.6 - the sanity kit is due out in about a week's
time, and this *might, just might* be fixed by something in there.

The sanity kit will also have the -38 Ladebug.

/Bevin