Re: Help Diagnosing Memory Leak

Help Diagnosing Memory Leak . . . stock perl 5.8.2 that ships with AIX 5.3

I use AIX 5.2 on my test machines and compile perl using gcc version 4.2.4. I have 12 different perl versions in /usr/local/bin/ directory. I keep the full version as part of the name, and do a symbolic link to the one I want to use. ( ln -s -f /usr/local/bin/perl5.12.2 /usr/local/bin/perl )

If you can do the same, perl 5.12.2 seems the best, fastest, etc, to date. Skip all of the perl 5.10.x versions. If you need to use 5.8.x then use at least 5.8.8. I don't remember why, but versions after 5.6.1 until 5.8.8 had problems ( maybe part of your experienced memory problem ).

Good Luck!

"Well done is better than well said." - Benjamin Franklin

Comment on Re: Help Diagnosing Memory Leak

Replies are listed 'Best First'.
Re^2: Help Diagnosing Memory Leak by Limbic~Region (Chancellor) on Mar 02, 2011 at 15:26 UTC
flexvault, Yes, I want to compile my own perl for a myriad of reasons but the top 4 are: Have a non-threaded version To be able to compile our own modules (we do not own the native AIX compiler) To compile a 64 bit version To take advantage of the features >= 5.10.0 Unfortunately, I am fighting a perpetual political battle and do not currently have anything other than the stock perl to play with. Cheers - L~R	[reply]
Re^3: Help Diagnosing Memory Leak by BrowserUk (Patriarch) on Mar 02, 2011 at 16:33 UTC
Argument: If you drive a 10 year old car, you get 10 year old fuel economy. In 2000, the average family car return 29 miles to the gallon and Petrol was 75p (uk) per gallon. Today, the average family saloon return 40+ per gallon, and petrol (gas) is Ł1.30 per gallon. Perl 5.8.2 was the second most buggy release of perl in the last decade and was released in November, 2003. A lot of unpaid, hard working and very clever guys have fixed whole bunch of bugs in the last 8 years or so. Allowing managerial indecision to prevent your company/department/operation from benefiting from their free-to-use efforts is mind-blowingly stupid. L~R. Cite me verbatim, with scepticism or condemnation as appropriate, but verbatim. It won't hurt me, but it might help you. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply]
Re^4: Help Diagnosing Memory Leak by Limbic~Region (Chancellor) on Mar 02, 2011 at 17:47 UTC
BrowserUk, I have no idea what you are talking about. I have only cited you once in this thread and it was verbatim. It was only to explain why I wasn't more helpful/friendly when I originally posted. I understood the issue could have been the environment which is why I included it in the root thread and which you went on to provide evidence to suggest it was in fact the case. I have re-read your response several times and in context of the entire thread and have no idea what you are talking about. Update: If your intent was as Anonymous Monk describes below, this makes so much more sense. I outlined some of what I am dealing with but can't be more explicit due to the nature of my work. One of my goals this year is to get 5.14 into the production environment which I will succeed at. Cheers - L~R	[reply]
Re^5: Help Diagnosing Memory Leak by Anonymous Monk on Mar 02, 2011 at 18:27 UTC
Re^6: Help Diagnosing Memory Leak by Limbic~Region (Chancellor) on Mar 02, 2011 at 18:32 UTC
Re^3: Help Diagnosing Memory Leak by flexvault (Monsignor) on Mar 02, 2011 at 18:19 UTC
Limbic~Region You have the best reason of all. . . better performance perl just gets better and better. ( It's already the best! :-) I have a threaded and non-threaded version of perl for each release. The AIX stock perl can co-exist with other versions, but keep in mind that you don't want to mix threaded / non-threaded libraries, so use the 'sh Configure -Dprefix=/...' for non-threaded versions, and use the default for the threaded versions or vice-versa. Use the first line of your script to define which version of perl to use, '#!/usr/local/bin/perl5.12.2-t -w' or '#!/usr/opt/bin/perl5.12.2-nt -w' You will have the same concerns/problems about libraries for 32-bit and 64-bit compiling. I use two different gcc compilers for 32/64 bit, and use a 3rd for downloading from CPAN. Good Luck! "Well done is better than well said." - Benjamin Franklin	[reply]