At the core of Win32::API are several small piece of assembler code: 

#if (defined(__BORLANDC__) && __BORLANDC__ >= 452)
    #define ASM_LOAD_EAX(param,type)  {   \
        __asm {                      \
            mov    eax, type param ; \
            push   eax             ; \
        }
/* MSVC compilers */
#elif defined _MSC_VER
    /* Disable warning about one missing macro parameter.
       TODO: How we define a macro with an optional (empty) parameter?
+ */
    #pragma warning( disable : 4003 )
    #define ASM_LOAD_EAX(param,type) { \
    __asm { mov eax, type param }; \
    __asm { push eax };            \
    }
/* GCC-MinGW Compiler */
#elif (defined(__GNUC__))
    #define ASM_LOAD_EAX(param,...)  asm ("push %0" :: "g" (param));
#endif

...
              ASM_LOAD_EAX(pParam, dword ptr); ## many similar

...

#if (defined(_MSC_VER) || defined(BORLANDC))
                __asm {
                    mov   eax, dword ptr [dParam + 4]  ;
                    push  eax                          ;
                    mov   eax, dword ptr [dParam]      ;
                    push  eax                          ;
                };
#elif (defined(__GNUC__))
/* probably uglier than necessary, but works */
asm ("pushl %0":: "g" (((unsigned int*)&dParam)[1]));
asm ("pushl %0":: "g" (((unsigned int*)&dParam)[0]));

/* { 
  int idc;
  printf ("dParam = ");
  for (idc = 0; idc < sizeof(dParam); idc++) {
    printf(" %2.2x",((unsigned char*)&dParam)[idc]);
  } 
  printf("   %f\n", dParam);
} */
#endif

[download]

One has to suspect, if the OP confirms he is using a mingw built version of Perl that the problem lies in there somewhere. Does mingw build using similar calling conventions to MSC? That is the PASCAL calling convention for system apis.

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.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^2: Win32::API Memory Exception with GetCommandLine() (which returns a static string) by BrowserUk
in thread Win32::API Memory Exception with GetCommandLine() (which returns a static string) by Wyrdweaver

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.