I don't know how Windows C++ works, but with GCC this error almost always
indicates you're using an object after it has been freed. The reason is that
freeing the object calls the destructors in inheritance order, and changes the
virtual method pointer table as it does so. The end result is a free object
whose vtable points to that of the earliest base class, with pointers to error
handlers for any pure virtual method.
So look for use-after-free errors.
paul
On Oct 3, 2012, at 2:29 AM, Mark Hammond wrote:
> [Please keep python-win32 in the CC list]
>
> On 3/10/2012 4:26 PM, vamsi krishna wrote:
>> Hi Mark,
>>
>> Thank you for the reply. Please let me know what kind of information
>> is useful in this context and I'm ready to provide the information.
>> At first I thought of assuming the same i.e. problem with HP QTP COM
>> libraries. But the question which is haunting me is this code
>> perfectly worked for almost one month and suddenly started creating
>> this problem. Still some times this code is working fine.
>
> But that doesn't point a finger in any specific direction either :(
>
> Probably what we need to know is the stack when this happens, but that is
> probably very hard to grab without MSVC or possibly one of the sysinternals
> tools...
>
> Cheers,
>
> Mark
>>
>> Best Regards,
>> Vamsi.
>>
>>
>> On Fri, Sep 28, 2012 at 5:52 AM, Mark Hammond <skippy.hamm...@gmail.com>
>> wrote:
>>> I'm afraid there isn't enough information provided here for us to help. At
>>> face value, it sounds like a problem in the HP QTP COM libraries.
>>>
>>> Mark
>>>
>>>
>>> On 25/09/2012 2:14 PM, vamsi krishna wrote:
>>>>
>>>> Hi,
>>>>
>>>> Running on Windows 2003 Server X64,Python 2.5 (32-bit)
>>>>
>>>> I am having problems using win32com.client with the HP QTP COM
>>>> libraries. I'm trying to launch QTP from python by following code:
>>>>
>>>> import win32com.client
>>>>
>>>> qtp = win32com.client.Dispatch("QuickTest.Application")
>>>> # starts up QTP
>>>> qtp.Launch()
>>>> qtp.Visible = False
>>>> time.sleep(30)
>>>> qtp.quit()
>>>>
>>>> At first it starts working without any glitches. but currently it is
>>>> always raising windows c++ error saying "pure virtual function call
>>>> R6025".
>>>>
>>>> Please provide information on how to tackle this issue.
>>>>
>>>>
>>>> Regards,
>>>> Vamsi.
>>>> _______________________________________________
>>>> python-win32 mailing list
>>>> python-win32@python.org
>>>> http://mail.python.org/mailman/listinfo/python-win32
>>>>
>>>
>
> _______________________________________________
> python-win32 mailing list
> python-win32@python.org
> http://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
