perl 5.10 yielding "Global destruction" errors while printing and Invoice in SQL-ledger, in OpenSUSE

mtiempos has asked for the wisdom of the Perl Monks concerning the following question:

Thank You for Your prompt reply, This is the error that I get at the bottom of the Invoice as I try to print , Attempt to free unreferenced scalar: SV 0x89b12e4, Perl interpreter: 0x8295008 during global destruction. I am using Perl5.10 straight from the installation Distro, in openSuse , Linux 2.6.31.5-0.1-desktop i686 , openSUSE 11.2 (i586). I called the programmers at SQL-Ledger, and they too commented that it was a problem with Perl5.10 , that I should use an older distro with Perl5.8 can You guide me to where I can ge the documentation for installing a previous version of Perl , and perhaps have both coexist? in the same server, for SQL-ledger use the 5.8 and for all YaST functions use the 5.10? Thank You again,

Comment on perl 5.10 yielding "Global destruction" errors while printing and Invoice in SQL-ledger, in OpenSUSE

Replies are listed 'Best First'.
Re: perl 5.10 yielding "Global destruction" errors while printing and Invoice in SQL-ledger, in OpenSUSE by moritz (Cardinal) on Dec 08, 2009 at 16:30 UTC
Don't try to uninstall the system perl, that will only cause trouble. If you think it's perl's fault, install a different perl version in a directory that's neither / nor /usr. But first you should be sure that it's a problem in the core of perl, and not in a module or code you're using. It might help if you tell us what code you run, and what error exactly you get. See also: How (Not) To Ask A Question.	[reply]
Re: perl 5.10 yielding "Global destruction" errors while printing and Invoice in SQL-ledger, in OpenSUSE by ikegami (Patriarch) on Dec 08, 2009 at 17:08 UTC
`valgrind` can be used to diagnose such problems	[reply] [d/l]
Re: perl 5.10 yielding "Global destruction" errors while printing and Invoice in SQL-ledger, in OpenSUSE by Anonymous Monk on Dec 08, 2009 at 16:29 UTC
Contact support for SQL-ledger or openSUSE	[reply]