Resent to the list without attachment since otherwise the message was too big. Sorry about that.
On Tue, Apr 6, 2010 at 1:03 PM, Abdullah Abouzekry <[email protected]> wrote: > i have it in the path but gets a different error > (kindly find attached image) when running each separate test, > your assistance is highly appreciated. :) > > Abdullah Abouzekry Hi Abdullah, I'm also replying on the list as it might be interesting for people running into the same issue later. The message error message from the image you attached was: The procedure entry point ?qver...@qtest@@ya_n_npbd...@z could not be located in the dynamic link library QtTest4.dll. That symbol refers to the decorated name of a function in QtTest (you can see this using the undname tool): Undecoration of :- "?qver...@qtest@@ya_n_npbd...@z" is :- "bool __cdecl QTest::qVerify(bool,char const *,char const *,char const *,int)" So for some reason, the QtTest4.dll file you're using is missing that function. My guess is you're using some older version of Qt or another dll than you think you're using. To debug the problem you can try the following: 1. load QtTest4.dll in Dependency Walker (depends.exe) 1.1. depends.exe comes with Visual Studio but you can also get it from here http://www.dependencywalker.com/ 1.2. if I open C:\Qt\4.6.2\bin\QtTest4.dll and I click it in the left tree, I see exactly the symbol you're missing as exported by the dll (see attached screenshot) so the symbol is there 1.3. if you also have the symbol in the dll you opened in Dependency Walker it probably means that your application is not using it but instead another dll with the same name that's also in your PATH 2. do you get this when running the tests from Visual Studio or the command line or both? You could also try the Qt command prompt. If you run Visual Studio as an administrator and cmd.exe as a regular user they could have different PATH settings. 3. finally, if you want to see exactly where QtTest4.dll is being loaded from you can use Process Monitor from here: http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx 3.1. create a filter on QtTest4.dll, run the tests and see the full path where the dll gets loaded from Catalin _______________________________________________ PySide mailing list [email protected] http://lists.openbossa.org/listinfo/pyside
