home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!haven.umd.edu!decuac!pa.dec.com!wsl.dec.com!klee
- From: klee@wsl.dec.com (Ken Lee)
- Newsgroups: comp.windows.x
- Subject: Re: Xerror - How to overcome it ??
- Message-ID: <1ikr7uINNei8@usenet.pa.dec.com>
- Date: 8 Jan 93 21:21:02 GMT
- References: <C0JnvM.4rA@ulowell.ulowell.edu>
- Reply-To: klee@wsl.dec.com
- Organization: DEC Western Software Laboratory
- Lines: 18
- NNTP-Posting-Host: alhambra.pa.dec.com
-
- In article <C0JnvM.4rA@ulowell.ulowell.edu>, vprasad@dragon (V G Prasad) writes:
- |> The reason for failing keeps changing
- |> eg _ X Error of failed request:
- |> BadLength (poly request too large or internal Xlib length error)
- |> 1. Major opcode of failed request: 6 (X_ChangeSaveSet)
- |> 2. Major opcode of failed request:10 (X_UnmapWindow)
- |>
- |> None of these functions are used in the code.
-
- Most likely you're somehow corrupting Xlib memory. Could be
- that you have a bogus pointer or are writing past the end of
- an array or outside an allocated memory block.
-
- --
- Ken Lee
- DEC Western Software Laboratory, Palo Alto, Calif.
- Internet: klee@wsl.dec.com
- uucp: uunet!decwrl!klee
-