X-Spam-Check-By: sourceware.org Date: Mon, 12 Jun 2006 13:11:54 -0400 (EDT) From: Igor Peshansky Reply-To: cygwin AT cygwin DOT com To: Thomas SMETS cc: cygwin AT cygwin DOT com, thomas DOT baker AT bi DOT fhg DOT de Subject: Re: Re : Re: Memory error with PDKSH 5.2.14-3? In-Reply-To: <20060612170427.18260.qmail@web32709.mail.mud.yahoo.com> Message-ID: References: <20060612170427 DOT 18260 DOT qmail AT web32709 DOT mail DOT mud DOT yahoo DOT com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Ugh, top-posting... Reformatted. On Mon, 12 Jun 2006, Thomas SMETS wrote: > From: Igor Pechtchanski > To: Thomas Baker > Cc: cygwin at cygwin dot com > Date: Mon, 6 Jun 2005 10:26:26 -0400 (EDT) > Subject: Re: Memory error with PDKSH 5.2.14-3? > > > On Mon, 6 Jun 2005, Thomas Baker wrote: > > > > > Just wanted to report that I was seeing error messages such as the > > > following in Korn shell scripts: > > > > > > /home/tbaker/u/bin/urlists[50]: internal error: alloc: freeing > > > memory outside of block (corrupted?) > > > > > > By running the scripts in debug mode (set -x), I found that > > > the problem seemed to occur when declared functions (i.e., > > > declared within the script) were invoked multiple times. > > > The functions would work at first, then stop working -- > > > as if the functions somehow ate up the available memory. > > > > > > Since rolling back from 5.2.14-3 to 5.2.14-2, the problem > > > seems to have gone away. > > > > > > I am not a programmer and do not have time to test this > > > systematically but thought others on this list might want > > > to hear about this. > > > > Thanks for the report. However: > > > > I have no hope of reproducing this, do I? > > > > AFAICS, the few changes from 5.2.14-2 to 5.2.14-3 that could have possibly > > caused this are the fixes in the autoconf files. I doubt the "struct > > option" magic would matter, but it's possible, I guess, though by > > eyeballing the code the two versions do look functionally equivalent. > > > > It would help to have a script that demonstrates the problem. I can't do > > anything otherwise, sorry... > > > > Igor Pechtchanski, the Cygwin pdksh volunteer maintainer > > One year later .... (with the same/latest version) > Using : > set -x > set -v > in a script generates a similar error around line 50whatever code I put > in the script Did you even read my reply to the OP? I cannot reproduce this without a complete testcase. Since I cannot reproduce this, there is no way I can fix this. Unless someone provides a complete testcase that exhibits this behavior, this problem will remain unfixed. Igor Peshansky, the Cygwin PDKSH volunteer maintainer -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!) |,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte." "But no -- you are no fool; you call yourself a fool, there's proof enough in that!" -- Rostand, "Cyrano de Bergerac" -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/