in reply to Perplexing message on command line.

Hi again.

I neglected to include the stack dump in my previous message: 

MSYS-1.0.17 Build:2011-04-24 23:39
Exception: STATUS_ACCESS_VIOLATION at eip=6083CF26
eax=00000000 ebx=00000022 ecx=00003A43 edx=FEFF0100 esi=00000000 edi=0
+0000061
ebp=0022FD70 esp=0022F6E8 program=us
cs=001B ds=0023 es=0023 fs=003B gs=0000 ss=0023
Stack trace:
Frame     Function  Args
0022FD70  6083CF26  (003E0000, 000F003F, 00012000, 003E0000)
0022FDB0  6083D3A8  (003E0000, 608F0104, 00011044, 00000000)
0022FF00  60855169  (6089C6C8, 00000000, 7C980620, 7C8021B9)
0022FF50  608042FC  (6089C7A0, FFFFFFFE, 000007D8, 6089C6A4)
0022FF90  60804B45  (00000000, 00000000, 00000001, 00000006)
0022FFB0  004040AF  (00401040, 037F0009, 0022FFF0, 7C81776F)
0022FFC0  0040103E  (00000010, 00000000, 7FFD5000, 805512FA)
0022FFF0  7C81776F  (00401000, 00000000, 78746341, 00000020)
End of stack trace

[download]


I have approximately 14,000 files under the root (C:/) folder and if I rename a file using the edit command, I notice a "pop-up" message saying "Out of near memory!", but I can click "Ok" and proceed. Since I have administrative privileges, this seems like a potential culprit.

Replies are listed 'Best First'.
Re^2: Perplexing message on command line.
by Anonymous Monk on Apr 24, 2013 at 09:33 UTC

    MSYS-1.0.17 Build:2011-04-24 23:39

    That doesn't spell ActiveState :)

    Manage your %PATH%

[reply]
      Hi all.

      Thanks for the help. Anonymous Monk, you're right ;)
      I am now able to compile C/C++ programs and run perl code *except* if the code contains the system command, e.g. 
      system("dir");

      [download]

      This results in the same message as my original post. I am starting to think the MinGW suite is causing a problem but I don't know enough about MSYS to make an accurate diagnosis. My path looks like the following:

      C:\;C:\perl\bin;C:\perl\site\bin;C:\MinGW\bin;...
      I am completely at a loss as far as how to proceed. Any suggestions would be most welcome! I solved the initial problem by deleting nearly all perl files in the root directly, e.g., perl5.8.8.exe, etc. since I am running 5.16.3. I can only hypothesize that the MinGW and/or MikTex installer copied several problematic files to the root folder and I simply haven't been able to isolate which one(s) they are.

      I foolishly deleted a file called msys-1.0.dll from my C:\ drive then copied the same file from the 'mingw' install directly, but the problem remains.

      Thanks,

      Cathy
[reply]
[d/l]

In Section Seekers of Perl Wisdom