home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #19 / NN_1992_19.iso / spool / comp / windows / x / 15934 < prev    next >
Encoding:
Text File  |  1992-08-31  |  2.0 KB  |  49 lines

  1. Newsgroups: comp.windows.x
  2. Path: sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!usc!cs.utexas.edu!sun-barr!ames!agate!iat.holonet.net!uupsi!psinntp!xilinx!kelem
  3. From: kelem@xilinx.com (Steve Kelem)
  4. Subject: epoch 4.1 crashes X11R4
  5. Message-ID: <1992Aug29.225739.28272@xilinx.com>
  6. Sender: usenet@xilinx.com
  7. Organization: Xilinx Inc.
  8. Date: Sat, 29 Aug 1992 22:57:39 GMT
  9. Lines: 38
  10.  
  11. I'm running epoch 4.1 on a Sparc 2, OS 4.1.1 with X11R4 under motif.
  12. I have two windows, the Minibuffer and a working window, arranged vertically
  13. the working window against the top of the screen, the Minibuffer against the
  14. bottom of the screen and a little space in between the two.
  15.  
  16. Every once in a while, while I'm typing in epoch, a rectangular area,
  17. containing both epoch windows, AND THE BACKGROUND IN BETWEEN THE TWO WINDOWS,
  18. is erased and the keyboard and mouse are rendered ineffective.  After 10 or 20
  19. seconds the X window system disappears and I'm logged off of the Sun.
  20. A core dump of XSun is left in my home directory.
  21.  
  22. adb prints the following call trace:
  23. core file = core -- program ``Xsun''
  24. SIGSEGV 11: segmentation violation
  25. $c
  26. _cfbFillBoxSolid(0x0,0xf770f120,0xfffffe86,0xfffffe87,0x0,0xffffffff) + 2a0
  27. _cfbPaintWindow(0xdd7f8,0xc1b90,0x0,0x0,0x0,0x1) + 16c
  28. _miSpritePaintWindowBackground(0xdd7f8,0xc1b90,0x0,0xffffffff,0x1a3,0xbd0e8) +
  29. 7
  30. 4
  31. _miClearToBackground(0xdd7f8,0xc1b90,0x200,0x2d0,0xfff2,0x0) + 140
  32. _miSpriteClearToBackground(0xdd7f8,0x2,0x200,0x2d0,0xfff2,0x0) + 120
  33. _ProcClearToBackground(0xe2298,0xf4,0x24,0x574,0xdd7f8,0x10c304) + a0
  34. _Dispatch(0xf7ffe998,0x0,0x10000,0xb8d4c,0xe2298,0x10) + 1c4
  35. _main(0x2,0xf7ffec64,0x1,0xae400,0x4,0x1) + 4ac
  36.  
  37.  
  38. Does anyone know what the problem is here?
  39. Thanks,
  40. /7\'7  Steve Kelem    (408)879-5347        kelem@xilinx.com
  41. \\ `   Xilinx                    FAX: (408)559-7114
  42. //     2100 Logic Drive
  43. \\/.\  San Jose, California 95124
  44. -- 
  45. /7\'7  Steve Kelem    (408)879-5347        kelem@xilinx.com
  46. \\ `   Xilinx                    FAX: (408)559-7114
  47. //     2100 Logic Drive
  48. \\/.\  San Jose, California 95124
  49.