Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 22 Oct 2002 08:05:27 -0400 From: Jason Tishler Subject: Re: Post-install script problems with latest snapshot In-reply-to: <20021021192858.GA19051@redhat.com> To: cygwin AT cygwin DOT com Mail-followup-to: cygwin AT cygwin DOT com Message-id: <20021022120527.GA992@tishler.net> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline User-Agent: Mutt/1.4i References: <20021021171328 DOT GA992 AT tishler DOT net> <20021021192858 DOT GA19051 AT redhat DOT com> Chris, On Mon, Oct 21, 2002 at 03:28:58PM -0400, Christopher Faylor wrote: > On Mon, Oct 21, 2002 at 01:13:28PM -0400, Jason Tishler wrote: > >With the latest snapshot (i.e., 2002-Oct-20) installed, I got a bunch > >of "can't read memory address foo" dialogs from things like basename, > >cp, rm, etc. while the post-install scripts were running. > > What was the exact error message? Shame on me for not taking a screen shot or jotting down the exact error messages because I can not reproduce the problem. FWIW, the dialogs with the error message look like the following: rm.exe - Application Error X The instruction at "foo" referenced memory at "bar". The memory could not be "read". Click on OK to terminate the program Click on CANCEL to debug the program Unfortunately, I do not remember what were the values of "foo" and "bar". However, I'm pretty sure that "bar" was in the low area of memory -- certainly not in the 0x61000000 range. Jason -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/