From: cgf AT bbc DOT com (Chris Faylor) Subject: Strange problem with Sergey's cygwin.dll and remote X 6 Jun 1997 12:11:26 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: Reply-To: cgf AT bbc DOT com X-Newsreader: trn 4.0-test57 (27 Apr 97) Original-To: gnu-win32 AT cygnus DOT com X-Mailer: Perl5 Mail::Internet v1.28 Original-Sender: owner-gnu-win32 AT cygnus DOT com I've recently installed Sergey's cygwin.dll and have been very happy with the performance improvement. I've noticed a strange interaction between it and a product I've been evaluating, however. The product is Nterprise. It is an add-on to Windows-NT which allows one to use Windows-NT applications on any X server. I've been evaluating this product for a few months and have been less than thrilled with its performance, but, for the most part, if you are willing to wait for windows to appear and if you are willing to try several times to "login", eventually you may get an almost usable NT window running on an X server. I had been using bash with no problem prior to updating to Sergey's cygwin. Now, whenever I start up a gnuwin remotely application it 'hangs' for an indefinite period. Reverting to stock B18 "cures" the problem. Obviously this is a problem with Nterprise, not cygwin, since the same software works perfectly when invoked locally. I'd like to be able to debug this problem, however, so that I can report back to the Nterprise folks with a specific function that is failing (I suspect that it has something to do with the querying of console colors or something like that). I am at a loss, however, as to how to debug this. I've built a cygwin.dll from scratch with Sergey's patches, but then, how do I debug it? Attempting to invoke gdb remotely hangs due to the problem I mentioned above. Attempting to start gdb with the "good" dll and start a test program with the "bad" dll just dies with stack failures or whatever -- this is the standard problem you see when you have two different versions of cygwin.dll in your path. So, how do I debug this? Certainly there must be some method for doing this or new cygwin.dll development is severely hampered. Any insight would be appreciated. -- http://www.bbc.com/ cgf AT bbc DOT com "Strange how unreal VMS=>UNIX Solutions Boston Business Computing the real can be." - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".