that's the conclusion i came to late last night too. now, for each of my XImage helper class instances, i declare a XShmSegmentInfo* in the ctor and point it to a new'd buffer so it hangs until the class dtor gets rid of it as my app is ending. seems to work okay for now. > Looking through the code, it looks like Xlib stores a pointer > to the shminfo. I didn't realize it did that. That would imply > that each XImage needs a XShmSegmentInfo that sticks around for the > life of the XImage. > > It impresses me that it is a mistake that it did this rather > than copying the contents of the XShmSegmentInfo. I'm not sure > why it was implemented that way. I don't think we have any > XShm man pages. If we did, hopefully, they would mention something > like that. > > The error must be that the first XImage ends up with the second > XImage's data and subsequently the operation appears to be addressing > outside of the shared memory segment, so the BadValue error happens. _______________________________________________ XFree86 mailing list XFree86@xxxxxxxxxxx http://XFree86.Org/mailman/listinfo/xfree86
