Well, print "hello\n" is enough to create the error msg

Really? 

C:\test>perl -e"print qq[Hello world\n]"
Hello world

[download]

Hm. No error message. What did I do wrong.

What perl did you have installed when you packaged the .par file? Is is possible that as a part of that packaging the .par file, you packaged up one or more dlls that are incompatible with your current Perl installation? And therefore when you run that .par, it unpacks that incompatible dll in such a way that it is found in preference to the equivalent dll that shipped with the installed version of perl?

In response to my explanation of how to discover which dll is the cause of the error, you told us

Just come from re-installing... No change! :-(

What did you reinstall?

  1. The same version of Perl--why would that make things change?
  2. The same pre-packaged .par file--ditto!
  3. Both?
  4. The OS?
  5. The carburetor on your motorbike?
Where to go from here ?

My suggestion would be to grab Process Explorer. Then re-run the .par file and when the error dialog with the error message is on-screen, switch to ProcExp and select "view->Lower Pane View->dlls", and "View->Show Lower Pane".

Then select the perl process running the .par file and click in the lower pane. Scroll the pane to the bottom and you will see all of the dlls being used by that process. If you mouse over perl510.dll you will get a tooltip showing you the full path to the dll that is failing to fulfill the Perl_croak_xs_usage() entrypoint.

I suspect that this will show that the perl510.dll in question is being unpacked from the .par file and is being loaded in preference to the perl510.dll that comes with your AS distribution. This is guesswork, but is the only thing I can think of (in the absence of the .par file and your installation), that might produce the symptoms you are describing.

You need to put some effort in and do some investigation. Saying print "hello\n" is enough to reproduce the problem belies the fact **THAT I HAVE AN ENTIRLEY DIFFERENT SET UP TO YOU AND THERFORE IT DOES NOT REPRODUCE ...

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)

In reply to Re^5: Perl_croak_xs_usage problem by BrowserUk
in thread Perl_croak_xs_usage problem by markuhs

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.