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 |
Hello, I have a question. My customer says his application program sometimes ( but not always ) aborts with the error Xtoolkit error Error in XMultiplex input %DWT-F-DWTABORT, .... He says he uses XT$APP_NEXT_EVENT and there may be some relation between this routine and error. But I don't know what causes the error, and how to avoid the abortion of the application. Will anyone give me some hints ? Thanks in advance, Kanako Inazu /TSC/CSC/CS/Japan
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
2224.1 | Just a guess... | LEOVAX::TREGGIARI | Wed Feb 07 1990 09:56 | 19 | |
> He says he uses XT$APP_NEXT_EVENT and there may be some relation between > this routine and error. There is definitely a relationship between XT$APP_NEXT_EVENT and the error. XMulitplexInput is the internal Xlib routine that the toolkit calls to wait for "input" (where "input" can be a X event, a timeout, or a source of alternate input - depending upon what the application has asked for). XMultiplexInput is called by the XtAppNextEvent routine which is called by XT$APP_NEXT_EVENT. The error the application is seeing is reported when XMultiplexInput returns an error status to the toolkit. Why would this happen? It doesn't ever *normally* happen (i.e. it's not a common error). My only guess would be that something is overwriting memory which holds the data that the toolkit sends to XMultiplexInput. The relevant data is the Application Context, the Xlib Display structure and any timeout or alternate input data structures. Leo | |||||
2224.2 | EWBV21::INAZU_K | It's a little bit funny | Mon Feb 12 1990 19:24 | 5 | |
Re. < Note 2224.1 by LEOVAX::TREGGIARI > Thank you for your information. Kanako Inazu |