Up Prev Next
From: philip dot c dot w dot chan at hsbcam dot com
Subject: Re: Problem with "attempt to free unreferenced scalar ......
Date: Nov 28 1998 11:14AM
Yes the qx command having problems are always involved date
manipulation like the following:
qx/date +"START:%d-%b-%Y %H:%M" > $global::lock_file/;
but not sure if that is what you mean by 'native format'.
From: "MIME:firstname.lastname@example.org" AT INTERNETMAIL on 11/27/98
To: Philip C W CHAN, SYBPERL-L@listproc.net AT
Subject: Problem with "attempt to free unreferenced scalar
This information (including any attached information) is issued by
a member of the HSBC Asset Management Group of companies for the
information of its non-private customers only. It is not an
invitation to buy or sell securities. HSBC Asset Management makes
no representation and accepts no responsibility or liability as to
its completeness or accuracy.
Each page attached hereto must also be read in conjunction with any
disclaimer which forms part of it.
> Recently I discovered the following error occurred to our
> perl/sybperl program:
> "Attempt to free unreferenced scalar at number>"
> The problem occurred approximately twice month and isn't
> to simulate. What I could see is, nearly all occasions the
> following command was involved:
> " = qx /date .... /"
> Has anyone ever came across the same problem? and most
> importantly, is there any way to fix it?
> We're running HPUX 10.20, perl version is 5.00404 and
> is 2.08.
> From the latest perl version 5.00502, I read from certain
> readme files about fixes on unreferenced memory problems, is
> this going to help?
I don't know.
However - do you use the UseDateTime attribute? I've just had another
error report with memory problems with perl 5.004_04 when using the
UseDateTime attribute (ie retrieving dates in native format).
Michael Peppler -||- Data Migrations Inc.
email@example.com -||- http://www.mbay.net/~mpeppler
Int. Sybase User Group -||- http://www.isug.com
Sybase on Linux mailing list: firstname.lastname@example.org