Re^5: Change in memory consumption when using debugger

As a testcase for a bug report it is still a little unweildy. Requiring a particular DB, a specific set of data etc.

I just looked at this again and noticed the comment

#  sample to illustrate strange behaviour on solaris 2.7
# (does not occur on solaris 2.8)
# (db names have been change to protect the innocent??)
[download]

If the problem is dependant upon the OS, assuming all else is equal, it seems likely that Perl is interacting badly with an OS (mis)feature. As such, it's unlikely to be something that Perl alone can fix. You're more likely to get a fix from Solaris than perl I think.

I admit I can't imagine what would lead to this set of symptoms, but I fixed OS bugs in the past that totally defied rationality -- until you knew what caused them.

There no chance of upgrading your test box to 2.8 I suppose?

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

Comment on Re^5: Change in memory consumption when using debugger Download Code

Replies are listed 'Best First'.
Re^6: Change in memory consumption when using debugger by Sandy (Curate) on Jul 05, 2004 at 13:40 UTC
Yes, I am also guessing that this is one weird interaction between any possible combination of 'odbc driver', perl, 'dbi module', 'dbd module', 'POSIX module', and stupid solaris 2.7. I'm pretty sure that no one will really want to take on this challenge for such a specific set of circumstances. Upgrading to solaris 2.8 (most logical solution to my problem) would require re-certifying the existing tools that currently reside on this machine (re-certification is absolutely necessary, and expensive). Solution #2 would be to change my code so that I don't need POSIX (used to get the password), and make the user pass the password on the command line, but of course that poses more security risks. Decisions, decisions, decisions....	[reply]
Re^7: Change in memory consumption when using debugger by BrowserUk (Patriarch) on Jul 05, 2004 at 13:45 UTC
Weird is right. Best of luck. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply] [d/l]