[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

2133.0. "XIO errors with V2" by DUGGAN::NOLAN (Susan Nolan, 297-4935) Wed Jan 24 1990 16:21

    
    A customer has upgraded to Decwindows T2.0-IFT2, and now they are
    getting Xlib IO error that they weren't getting with V1.0.
    
    It happens with local transport on VS3100, with the following message:
    
    [_XInputArrival-input buffer pointer not empty during processing]
                   -State: 2  flags: 0  stopDepth: 0]
    followed by SS$_BADPARAM VMS message
    
    
    Also get the following error using local transport under v2:
    
    XIO: fatal IO error 65535 on server XXXXX::0.0
         after nnnn requests (mmmm known processed) with 0 events remaining.
    %XLIB-F_IOERROR, xlib io error
    -DECW-F-ILLFORMED_XTCB, transport buffer has invalid header
    
    Xlib: sequence lost ()x3eccd >0x2ed26) in reply type 0x0!
    This is generally followed by an ACCVIO.
    
    Haven't been able to pinpoint what is the source of the problem?  Any
    hints/ideas as to when these errors might occur may help in debugging
    it.  They don't have an isolatable piece of code to reproduce this.
    
    Any information is appreciated.

T.R	Title	User	Personal Name	Date	Lines
2133.1		STAR::MFOLEY	Rebel Without a Clue	`Thu Jan 25 1990 00:45`	8
	Ummmm, I'd like to know how the customer upgraded to T2.0-IFT2. What version of VMS? Why aren't they running VMS 5.3 that has the SSB version of DECwindows V2.0?? mike
2133.2		DECWIN::JMSYNGE	James M Synge, VMS Development	`Thu Jan 25 1990 09:55`	19
	I too wonder why your customer is using T2.0-IFT2. It isn't supported anymore. All of our fieldtest sites have been upgraded to VMS V5.3. How did this customer get the version they're running???? >Also get the following error using local transport under v2: > >XIO: fatal IO error 65535 on server XXXXX::0.0 > after nnnn requests (mmmm known processed) with 0 events remaining. >%XLIB-F_IOERROR, xlib io error >-DECW-F-ILLFORMED_XTCB, transport buffer has invalid header One of the internal data structures of the transport layer has been corrupted. The header of an XTCB, which is user writeable, has been corrupted. I'd be inclined to suspect that your customer's program has a bug in it which is causing it to overwrite memory it didn't allocate. James
2133.3		DUGGAN::NOLAN	Susan Nolan, 297-4935	`Thu Jan 25 1990 11:35`	13
	They have upgraded to VMS 5.3, I had inaccurate information. They first saw the problem with T2.0-IFT2 and they still have it with VMS 5.3. They accept that it probably is a bug in their application, but they need help in trapping it. If they ran it with sync mode turned on, would there be a signal sent to the debugger to pinpoint which thread of code is causing the problem? They are looking for more detail on what could generate this error so they can focus their debugging effort?
2133.4		DECWIN::JMSYNGE	James M Synge, VMS Development	`Thu Jan 25 1990 16:46`	12
	Sync mode might help tracking the bug down, but is no gaurantee. In particular, sync mode would change the order in which the XTCBs are used, so that one might be corrupted, but it wouldn't be detected until later. > If they ran it with sync mode turned on, would there be a signal sent > to the debugger to pinpoint which thread of code is causing the > problem? No. James
2133.5		COMICS::FISCHER	UK Workstations Support	`Tue May 29 1990 11:54`	9
	Could someone please explain the error mentioned in .0 ie.... [_XInputArrival-input buffer pointer not empty during processing] -State: 2 flags: 0 stopDepth: 0] I can't find it documented anywhere. Ian