Conference bulova::decw_jan-89_to_nov-90

3538.0. "Xt$initialize looses traceback info ?" by BLKPUD::THOMASA (Wow I,ve got a colour ....) Fri Oct 26 1990 13:12

Hi all,
	I have a customer with a large application that running as a detached
 process on VMS.(5.3-1)
	The application is a DECwindows beast using UIL. The problem is that
when he exceeds a certain number of widgets within his UIL file the program
access violates somewhere -- but no trace back info is given in the 
/error=logfile  (linked with traceback)

	In trying to track down the cause of 

a. the lack of traceback info &
b. why the program access violates

this my customer has done at the start of his code :-

1. 					& 2.
.
.
call lib$signal(%val(ss$_accvio))       call xt$initialize(...) 
call xt$initialize(...)                 call lib$signal(%val(ss$_accvio)) 
.
.
.

1. produces tracebackinfo in the log file
2. does not !!!!

qun: What should I look for to determine why the call to xtinitialize is
 disabling the traceback info ???

	Also I notice that he has been calling XtPending from within an AST
and says he's had no problems so far... I thought the toolkit was non-ast
 re-entrant -- is he just living on borrowed time ?

		Andy