in reply to Attempt to free unreferenced scalar...

That error message usually indicates a bug in Perl. You should try to narrow down the problem by removing code from your program. Then when it is as small as you can make it while still demonstrating the problem, you should send a complete report to perlbug@perl.org

One thing that sometimes causes this error are: Buggy XS modules. Another is when you try to do too much stuff in a signal handler function. Do you have any signal handlers in your program?

  • Comment on Re: Attempt to free unreferenced scalar...

Replies are listed 'Best First'.
Re: Attempt to free unreferenced scalar...
by Daniellek (Sexton) on Nov 30, 2000 at 14:58 UTC
    Ok, i'll try narrowing code, and checking if it still crashes :)

    But still have a question: is it possible that buggy module can cause "my" error in the place of code where it is not used?

    And I don't do much with signal handlers in my code so I think it's not the problem (but I'll try to check this of course!)

    Thanks. 

    -- 
Daniellek

    [download]
[reply]
[d/l]
      daniellek says:

      <blcokquote> > is it possible that buggy module can cause
      > "my" error in the place of code where it is not used?

      Yes, that's exactly why it is so hard to track down this sort of bug. Memory is corrupted in one place and then the probably does not manifest until later on.

[reply]
        Okey, I cut it down from almost everything :)

        modules used are: strict, Carp and Socket. And the problem still exists (so i can assume mime-tools are bug-free which makes mi happy :)

        I stripped it also of connecting to mySQL database

        There are now about 150 lines which make forking/multithreading and these parts with opening "ls" and "find"

        And I don't know what to do further...

        Should I post the code here? 

        -- 
Daniellek

        [download]
[reply]
[d/l]

In Section Seekers of Perl Wisdom