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

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

2401.0. "Mulitthreaded Xlib appl. and XSetIOErrorHandler, how to do it ?" by KAL::BJERKEHOLT (Bo Bjerkeholt, TPSG, SWAS, @GOO) Wed Mar 07 1990 13:45


	We're writing a multithreaded xlib application and want's to be alive
	no matter what. 

	According to the manual the own I/O error handler specified can NOT
	return. If it does the client exits. Using the defaulthandler gives
	the same results.

	This means that if any of our servers crashes, or the net is 
	disconnected or poweroff on a Dwt, etc, the application will exit.

	Anyone have any hints on how to stay alive. Using longjmp or .....?

	hopes for hints

	Regards,
		Bo
T.RTitleUserPersonal
Name		DateLines
2401.1Sorry...DECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Wed Mar 07 1990 17:548
    I don't think there is a good way.  This was a serious design error.
    I don't know if it can be fixed or not, but be consoled by the fact
    that all X people have this problem.
    
    I suggest a QAR to let people know that this is important to you.
    
    Burns
2401.2Is it implented in VMS at all ??KAL::BJERKEHOLTBo Bjerkeholt, TPSG, SWAS, @GOOFri Mar 09 1990 09:0912

	Thanks for the answer even though I didn't like it. I can agree
	that this is a major design error. 

	I doubt that setting up an own IOErrorHandler is implemented at
	all in VMS. At least my IOerror handler didn't get called. 

	Next step will be to set up an own condition handlers and ......
	something clever.

	/bo
2401.3It isDECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Fri Mar 09 1990 14:059
Yes, it is certainly implemented.  I've not used it myself, but others have.
If it never even gets called, another QAR is due.

I'm not sure a condition handler will help you much, although if you can figure
out how far to unwind the stack to get back to the application, you might
have some chance of continuing (not sure though...you may end up with ASTs
disabled and other gungy stuff.  You will certainly leak some memory).

Burns