This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: Cygwin/X just now started to crash with Solaris app, 8bpp UPDATE
- From: "Sebastian" <sebastianhaby at home dot se>
- To: cygwin-xfree at cygwin dot com
- Date: Wed, 20 Oct 2004 16:51:08 +0200
- Subject: Re: Cygwin/X just now started to crash with Solaris app, 8bpp UPDATE
- Reply-to: cygwin-xfree at cygwin dot com
Hello again!
I've been doing debugging and testing the last two days, and things are weird ;)
When running XWinEMU2 from gdb with mwm it both works and crashes.
(run -ac -screen 0 1280 1024 -emulatepseudo)
Program received signal SIGSEGV, Segmentation fault.
0x000000ff in ?? ()
(gdb) bt
#0 0x000000ff in ?? ()
#1 0x006974be in shadowPaintWindow ()
#2 0x00493fd5 in miClearToBackground ()
#3 0x00497caf in miSpriteClearToBackground ()
#4 0x00409c83 in ProcClearToBackground ()
#5 0x00428f93 in SProcClearToBackground ()
#6 0x004078a2 in Dispatch ()
#7 0x004014b1 in main ()
(gdb)
When running XWinDEBUG from inside gdb with fvwm2 it both works and crashes!
Program received signal SIGSEGV, Segmentation fault.
0x00000099 in ?? ()
(gdb) bt
#0 0x00000099 in ?? ()
#1 0x007836a9 in shadowPaintWindow(pWindow=0x10372188, prgn=0x22eae0, what=0) at shadow.c:1294
#2 0x004be52f in miClearToBackground (pWin=0x10372188, x=0, y=0, w=0, h=0, generateExposures=0) at miwindow.c:131
#3 0x004b9d0b in miSpriteClearToBackground (pWin=0x10372188, x=0, y=0, w=0, h=0, generateExposures=0) at misprite.c:948
#4 0x0040c5eb in ProcClearToBackground (client=0x10395f38) at dispatch.c:1712
#5 0x00436e32 in SProcClearToBackground (client=0x10395f38) at swapreq.c:658
#6 0x00409864 in Dispatch () at dispatch.c:454
#7 0x00401644 in main (argc=6, argv=0x100e1b68, envp=0x100e00a8) at main.c:440
Is there anyone out there who can give me some pointers as where to start looking for the bug.
>From the dgb output I plan to start looking into the shadowPaintWindow () function as that function seem to be causing the following "0x000000ff in ?? ()" error?
Cheers,
Sebastian Haby3d0) at shadow.c:1294
#2 0x004be52f in miClearToBackground (pWin=0x10372188, x=0, y=0, w=0, h=0, generateExposures=0) at miwindow.c:131
#3 0x004b9d0b in miSpriteClearToBackground (pWin=0x10372188, x=0, y=0, w=0, h=0, generateExposures=0) at misprite.c:948
#4 0x0040c5eb in ProcClearToBackground (client=0x10395f38) at dispatch.c:1712
#5 0x00436e32 in SProcClearToBackground (client=0x10395f38) at swapreq.c:658
#6 0x00409864 in Dispatch () at dispatch.c:454
#7 0x00401644 in main (argc=6, argv=0x100e1b68, envp=0x100e00a8) at main.c:440
Is there anyone out there who can give me some pointers as where to start looking for the bug.
>From the dgb output I plan to start looking into the shadowPaintWindow () function as that function seem to be causing the following "0x000000ff in ??