[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: PerlModule B::TerseSize causes Prototype mismatch: sub B::OP:size:none vs () error

Archer Barrie wrote:

Thank you for that resource. I found it suspicious that even at the other location the B::TerseSize line was set off from the rest. Apache::Status seems to be pulling the module in via b_terse_size_link.

I have been trying to use this process for determining sizes but with
limited success. You don't say whether the output /perl-status produces is

That's because I'm still trying to evaluate it to determine if it is. :) It seems to produce output and not crash for the most part. I think it's only crashed when I've tried to pull in B::TerseSize.

Can you successfully use Memory Usage?

It also seems to work. I haven't had a crash yet, but I haven't tried every module under the sun. I've tried Apache, Apache::Status, CGI, DBI and HTML::Mason::ApacheHandler to name a few.

If you have a stock module or three that always cause the Memory Usage report to crash I could give them a try.

kernel-image-2.6.8-i386 2.6.8-16sarge2
apache 1.3.33-6sarge1
libb-size-perl 0.05-1
perl 5.8.4-8sarge3


Reply to: