--- [EMAIL PROTECTED] wrote:
> On Sun, 30 Apr 2000 19:12:52 -0700 (PDT), [EMAIL PROTECTED] wrote:
> > All,
> >
> > In the GSDepthForScreen and GSAvailableWindowDepthsForScreen functions I
> > neglected to put in an XCloseDisplay call to close the connection to the
> > X server. This doesn't seem to cause any huge problem, but the messages
> > are annoying. I am working on a fix as I write this message. It should
> > be ready either tonight or sometime tomorrow.
>
> I fixed that problem last week - but probably not the best way - it seems to
> me that the screen stuff *ought* to be able to use the display handle from the
> graphics context object rather than having to open/close the display -
> however, when I tried doing that, my test app crashed (though it might just
> have been a silly mistake on my part) and I didn't have time to investigate
> properly.
The reason your test app crashed was because of the fact that I was doing an XFree
on the Screen structure returned by XScreenOfDisplay. As it turns out this
structure is stored by the server. If it is freed, then any time
that structure is accessed, you will get a segmentation fault. The memory
held by this structure is released when the display is closed.
I have tested my patch with all of the applications in the Testing directory.
Everything looks good.
Thanks,
=====
Gregory John Casamento -----------------------
"C makes it easy to shoot yourself in the foot;
C++ makes it harder, but when you do it blows
your whole leg off."
- Bjarne Stroustroup
__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/
