Maybe some of the circular reference finding tools like Devel::Leak,
Devel::Peek, or Devel::LeakTrace::Fast can help?
- Perrin
On Wed, Jun 13, 2012 at 4:35 PM, Josh Narins wrote:
> I have a DESTROY method I can’t avoid keeping around, and in certain code
> paths in mod_perl I successfully make s
I have a DESTROY method I can't avoid keeping around, and in certain code paths
in mod_perl I successfully make sure all instances are cleaned up before my
final save, and all is well.
For another page, however, apparently, there is still a reference to it lying
around after I undef the two cop
On Wed, Jun 13, 2012 at 7:04 AM, Chris Kaltwasser wrote:
>
> looks like your CPU does not support an instruction the library is
>> trying to use. Or the lib is corrupted.
>>
>> What does "cat /proc/cpuinfo" say?
>>
>> Thanks for the suggestion. I've pasted that output below. But, wouldn't a
> mor
> looks like your CPU does not support an instruction the library is
> trying to use. Or the lib is corrupted.
>
> What does "cat /proc/cpuinfo" say?
>
> Thanks for the suggestion. I've pasted that output below. But, wouldn't a
more likely cause for an illegal instruction be some bug in modperl, fo
