This is the mail archive of the
mailing list for the Cygwin project.
Re: Re : Re: Memory error with PDKSH 5.2.14-3?
- From: Igor Peshansky <pechtcha at cs dot nyu dot edu>
- To: Thomas SMETS <smetsthomas at yahoo dot com>
- Cc: cygwin at cygwin dot com, thomas dot baker at bi dot fhg dot de
- Date: Mon, 12 Jun 2006 13:11:54 -0400 (EDT)
- Subject: Re: Re : Re: Memory error with PDKSH 5.2.14-3?
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
Ugh, top-posting... Reformatted.
On Mon, 12 Jun 2006, Thomas SMETS wrote:
> From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
> To: Thomas Baker <thomas dot baker at bi dot fhg dot de>
> 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: 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
|\ _,,,---,,_ email@example.com | firstname.lastname@example.org
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