Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Sun, 24 Oct 1999 21:05:19 -0400 To: Brian Kasper Cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: X11R6.4 for Cygwin Release v1.0? (And thanks) Message-ID: <19991024210519.A8798@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: Brian Kasper , cygwin AT sourceware DOT cygnus DOT com References: <19991024164429 DOT 20269 DOT qmail AT wwcst088 DOT netaddress DOT usa DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19991024164429.20269.qmail@wwcst088.netaddress.usa.net>; from Brian Kasper on Sun, Oct 24, 1999 at 09:44:29AM -0700 On Sun, Oct 24, 1999 at 09:44:29AM -0700, Brian Kasper wrote: >Chris Faylor wrote: >I have to assume the STATUS_ACCESS_VIOLATION error is due to >some incompatibility between the B20 DLL's or libraries and >those from the 1.0 release -- the program experiencing the >error compiles and runs without error using There's an incredibly easy way to tell -- run the program under gdb. There's no reason to assume anything. > B20.1 and Mr Siddiqi's B20-specific X11R6.4/Lesstif > Microsoft Visual C++ 6.0 and X11/Motif libs from Hummingbird > XFree86 / Lesstif on both Intel and Alpha Linux boxen > >so I don't *think* the error is in my code. I also recompiled >everything I could (my own executable code and my library code); >the only important part I have not recompiled is the >X11R6.4/Lesstif stuff. > >In short, I get an error-free link with code that I trust pretty >well, and it dies due to an S_A_V error every time I run it under >release 1.0. Not to appear argumentative, Chris, but I'm not sure >your statement "if it links, you're ok" is 100% true. I guess we'll never know if you are unwilling to actually debug the problem. Sadly, since there is no more data than "It doesn't work" I guess I can guarantee that you'll experience the same problem when the next release comes out in a few weeks. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com