Topic
  • 2 replies
  • Latest Post - ‏2011-09-15T17:39:11Z by JerryCallen
JerryCallen
JerryCallen
9 Posts

Pinned topic Quantify loops at program startup (Windows7 64-bit, 32-bit C++ application)

‏2011-09-15T14:58:30Z |
I'm working with the 7.0.1 evaluation version of PurifyPlus for Windows on Windows7, 64-bit, trying to get a 32-bit C++ application running under Quantify. Quantify loops at startup after completing the instrumentation of the executable and DLLs. The stack traceback (from process explorer) is:

ntdll.dll!NtQueryVirtualMemory+0xa
wow64.dll!Wow64EmulateAtlThunk+0x6562
wow64.dll!Wow64EmulateAtlThunk+0x6863
wow64.dll!Wow64SystemServiceEx+0xd7
wow64cpu.dll!TurboDispatchJumpAddressEnd+0x2d
wow64.dll!Wow64SystemServiceEx+0x1ce
wow64.dll!Wow64LdrpInitialize+0x429
ntdll.dll!RtlUniform+0x6e6
ntdll.dll!RtlCreateTagHeap+0xa7
ntdll.dll!LdrInitializeThunk+0xe
ntdll.dll!NtQueryVirtualMemory+0x12
KERNELBASE.dll!VirtualQuery+0x15
PUREQRT.DLL!_x_q_cancel_indirect_call+0x1c68a

It appears that execution isn't even getting to main(), as the code sends a message to cerr immediately upon entry to main(). The following messages (that look harmless to me) are produced in the "Run Summary" messages tab:

Failure to allocate requested space for run-time data.
run-time data base 0x0 and run-time data size 0x10000000.
Using -runtime_data_base=0x20510000 and -runtime_data_size=0xfc50000 instead.

The code does run under Purify.

If I can't get this working, there won't be much point in us purchasing the product. Any help would be appreciated.
Updated on 2011-09-15T17:39:11Z at 2011-09-15T17:39:11Z by JerryCallen
  • SystemAdmin
    SystemAdmin
    2948 Posts

    Re: Quantify loops at program startup (Windows7 64-bit, 32-bit C++ application)

    ‏2011-09-15T16:49:25Z  
    Hi Jerry,

    >
    > Failure to allocate requested space for run-time data.
    > run-time data base 0x0 and run-time data size 0x10000000.
    > Using -runtime_data_base=0x20510000 and -runtime_data_size=0xfc50000 instead.
    >

    Have you tried using the suggestion options? It appears that Quantify is perhaps
    running out of memory. You can set these options under "Additional Options" in
    the Quantify settings. (see attached image).

    Also, be sure to check out the performance and scalability tips on DeveloperWorks:
    http://www.ibm.com/developerworks/rational/library/07/0313_cherkasov/

    Finally, there's always the possibility that this problem is specific to 64-bit
    Windows 7. PurifyPlus has never been officially tested on 64-bit Windows, and
    while PurifyPlus seems to work fine with 32-bit apps on 64-bit Windows, it really
    has not been thoroughly tested on 64-bit Windows. So, if you have any 32-bit
    Windows machines lying around, it might be worth it to install PurifyPlus there to
    see if the results are any different.

    Regards,
    Don
  • JerryCallen
    JerryCallen
    9 Posts

    Re: Quantify loops at program startup (Windows7 64-bit, 32-bit C++ application)

    ‏2011-09-15T17:39:11Z  
    Hi Jerry,

    >
    > Failure to allocate requested space for run-time data.
    > run-time data base 0x0 and run-time data size 0x10000000.
    > Using -runtime_data_base=0x20510000 and -runtime_data_size=0xfc50000 instead.
    >

    Have you tried using the suggestion options? It appears that Quantify is perhaps
    running out of memory. You can set these options under "Additional Options" in
    the Quantify settings. (see attached image).

    Also, be sure to check out the performance and scalability tips on DeveloperWorks:
    http://www.ibm.com/developerworks/rational/library/07/0313_cherkasov/

    Finally, there's always the possibility that this problem is specific to 64-bit
    Windows 7. PurifyPlus has never been officially tested on 64-bit Windows, and
    while PurifyPlus seems to work fine with 32-bit apps on 64-bit Windows, it really
    has not been thoroughly tested on 64-bit Windows. So, if you have any 32-bit
    Windows machines lying around, it might be worth it to install PurifyPlus there to
    see if the results are any different.

    Regards,
    Don
    I added the suggested options to the "Additional Options" area of the settings dialog box, and now it runs. Thanks!

    FWIW - The way the message is worded suggests that those options had been automatically applied, which is why I presumed they were harmless.