Yaakov (Cygwin/X) wrote: Jon TURNEY wrote: So I guess suspicion first falls that this leak is somewhere in one of the updated X DLLs... The question is then, how can we track this down? This actually turned out to be easier to track down than I thought. Using process explorer on 'wmaker
2009/1/27 Jon TURNEY jon.tur...@dronecode.org.uk: Jana Skleničková wrote: I upgraded to latest (I believe) version of Cygwin (uname -a=CYGWIN_NT-5.1 my_computer_name 1.5.25(0.156/4/2) 2008-06-12 19:34 i686 Cygwin) and after that I experience problem running XWin to a computer running Solaris
Here's a copy of a post I sent previously about Solaris and X server issues. Could be useful in this context. -- Snip -- You know, as it so happens, I've been tracking down a solution to a similar problem I just started experiencing today.
Hi, I was intrigued by this one, but could not reproduce. In Xming I got a crash due in -internalwm mode due to a message handler collision (WM_WM_MAP(2) was shared badly). I fixed this by adding yet another handler, i.e. WM_WM_MAP3, to give separation.. This is probably not related. Thanks
Howdy! I have a pretty interesting problem, I installed a new version of matlab on an ubuntu linux box. Two users in my group are using cygwin on their PC's to connect and export the matlab displays back to their local machines. Both users are having problems with the Matlab gui; both are