#818 PopFile 1.1 under Vista

[Grzegorz Skoczylas]

I'm successfully using the latest version of the PopFile under Windows Vista Professional. Recently, during tracing execution of my application (I'm software developer) I found that PopFile is generating many error messages using OutputDebugString function.

I'm using TraceTool for monitoring my application. Below there is part of log generated by the PopFile:
18:41:06:764 popfile.exe Invalid parameter passed to C runtime function.
18:41:06:768 popfile.exe Invalid parameter passed to C runtime function.
18:41:06:771 popfile.exe Invalid parameter passed to C runtime function.
18:41:06:996 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:001 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:004 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:007 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:011 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:014 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:018 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:022 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:026 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:029 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:033 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:038 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:246 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:250 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:253 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:256 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:260 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:264 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:267 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:271 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:275 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:280 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:326 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:330 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:510 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:513 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:517 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:520 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:523 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:526 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:530 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:534 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:538 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:543 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:547 popfile.exe Invalid parameter passed to C runtime function.
18:41:07:550 popfile.exe Invalid parameter passed to C runtime function.

[Brian Smith]

This is a problem with the version of Perl that is used in that version of POPFile.

You can get the same sort of output from a simple Perl script which accesses a webpage, as discussed in Ticket 45 on our website ( http://getpopfile.org/ticket/45 )

This Perl problem was fixed a few days ago when ActivePerl 5.8.9 Build 826 was released (25 May 2009) therefore the next release of POPFile (1.1.1) will not generate these "Invalid parameter passed to C runtime function" messages.

The first release candidate for POPFile 1.1.1 is now available, as announced on our homepage.

Brian