Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!snorkelwacker!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse From: mouse@LARRY.MCRCIM.MCGILL.EDU Newsgroups: comp.windows.x Subject: Re: Attempting to interpret X application error msg Message-ID: <9010110203.AA05441@Larry.McRCIM.McGill.EDU> Date: 11 Oct 90 02:03:41 GMT Sender: root@athena.mit.edu (Wizard A. Root) Organization: The Internet Lines: 51 > A non-technical user at my site is [...] getting the following error > msg: > X Error: BadValue, integer parameter out of range for operation > Request Major code 1 () > Request Minor code > ResourceID 0x3c > Error Serial #226 > Current Serial #253 > How would I go about finding out what the problem is with this, > without access to the source code of the application? Well, my first comment would be something along the lines of "what are you doing running it if you don't have source to it", but that's more evangelistic than helpful. If the binary has been stripped, about your only choice is to use something like xscope to follow the protocol requests and replies. Major request 1 is CreateWindow; there are a great many things that could be causing a BadValue error from CreateWindow. If the binary hasn't been stripped, you can get more information with a debugger. Patch the _Xdebug variable to non-zero and set a breakpoint at exit. Then when the program dies ask for a stack trace. Under adb, for example, % adb somexprog (Setting a breakpoint at main is necessary on Sun release 4 due to a bug[%] in the shared libraries implementation, or perhaps in adb: adb thinks __Xdebug doesn't exist until the program has started.) _main:b :r breakpoint _main: __Xdebug/W 1 __Xdebug: 0x0 = 0x1 _exit:b :c ... X error message here breakpoint _exit: $c and the stack trace should give you some idea what's wrong. [%] I hold it to be a bug. I doubt Sun thinks so - which to my mind is a problem with Sun. der Mouse old: mcgill-vision!mouse new: mouse@larry.mcrcim.mcgill.edu