Path: utzoo!mnetor!uunet!lll-winken!ubvax!vix From: vix@ubvax.UB.Com (Paul Vixie) Newsgroups: comp.windows.x Subject: debugging with the toolkit Message-ID: <6570@ubvax.UB.Com> Date: 1 Apr 88 23:28:03 GMT Reply-To: vix@ubvax.UUCP (Paul Vixie) Organization: Ungermann-Bass Enterprises Lines: 24 Bad news from my latest experiment: # X Protocol error detected by server: integer parameter out of range # Failed request major op code 1 X_CreateWindow # Failed request minor op code 0 (if applicable) # ResourceID 0x0 in failed request (if applicable) # Serial number of failed request 32 # Current serial number in output stream 52 This occurs after I've set up all the widgetry and called XtMainLoop(). When I get these from an XtRealizeWidget() or XtCreateManagedWidget() I can look hard at the widget I just created. In this instance I don't quite know where to look. So: how do I find out more about this error? Perhaps if I can dump out the whole X_CreateWindow message I can find the parameter that's in error and work back to locating the problem in my code. I'm going to go peruse the source to see if there's a wizardly debugging mechanism for this... But even if I find the answer, I thought the question (and any answers to it) would be generally useful to others. -- Paul Vixie Consultant Work: 408-562-7798 vix@ub.com vix%ubvax@uunet.uu.net Ungermann-Bass Home: 415-647-7023 {amdahl,ptsfa,pyramid,uunet}!ubvax!vix Santa Clara, CA <>