I am getting the below error only when I try to create child process using fork in the code mentioned in this Thread.


Engine::_Execute(..\..\perl\modules/Engine.pm:122):
122: unless (fork) {
  DB<1> s
Bizarre SvTYPE [37] at ..\..\perl\modules/Engine.pm line 122.
Engine::_Execute(C:/Perl/lib/Carp.pm:97):
97:  { local $@; require Carp::Heavy; }  # XXX fix require to not clea
+r $@?

[download]


It means there are some localized scalar variables are trying to restore in a child process hence throwing error


"Attempt to free unreferenced scalar"


There is some modules where carp.pm is used. I replaced all the places of carp with warn and tried
but no luck still it is showing the same. Please let me know how to debug this issue.

In reply to Re^2: Setting break point for particular condition in the subroutine by srlbharu
in thread Setting break point for particular condition in the subroutine by srlbharu

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.