Re: Tracking down DLL load errors in Windows ?
Mark Tolonen metolone+gm...@gmail.com said : Yes, welcome to Microsoft's solution to DLL Hell...Side-by-Side DLL Hell. As always, it boils down to a philosophical choice : is it better to suffer through Hell alone, or in bad company ? :-) -- http://mail.python.org/mailman/listinfo/python-list
Re: Tracking down DLL load errors in Windows ?
Fred P xne...@fredp.lautre.net said : Hi, a bit of platform-specific advice sought here... I'm trying to diagnose one of those mysteries Windows is so fond of... Say that I have code that imports some binary Python module from site- packages (in this case, libpyexiv2.pyd through pyexiv2.py, could be anythng else). On three Windows boxes I've tried it (XP Pro or Home, Python 2.5) everything works fine. On a fourth, importing the module fails with a traceback like this : Traceback (most recent call last): File stdin, line 1, in module File c:\python\lib\site-packages\pyexiv2.py, line 60, in module import libpyexiv2 ImportError: DLL load failed: This application could not start because its configuration is incorrect. Reinstalling it might solve the problem. I have tried long and hard to spot a meaningful difference between the first three systems and the last, without success. Is there any tool and/or methodology I could use to at least pinpoint the exact DLL that libpyexiv2 is failing to load, and ideally also the reason why ?... Thanks to Mark and Christian : dependency-walker confirmed the VC++ issue. After installing the MS redistributable DLL package -- actually I had to install *three* before hitting the right one (2005SP1) -- libpyexiv2 finally loads all its dependencies. Of course I've still no idea why/how it ran on the first three systems (and most others, from the look of it) without doing anything, and not on this one... but at least now it works :-) -- http://mail.python.org/mailman/listinfo/python-list
Re: Tracking down DLL load errors in Windows ?
Fred Pacquier xne...@fredp.lautre.net wrote in message news:xns9ca8b91a1519apacmanr...@212.27.60.38... After installing the MS redistributable DLL package -- actually I had to install *three* before hitting the right one (2005SP1) -- libpyexiv2 finally loads all its dependencies. Of course I've still no idea why/how it ran on the first three systems (and most others, from the look of it) without doing anything, and not on this one... but at least now it works :-) Yes, welcome to Microsoft's solution to DLL Hell...Side-by-Side DLL Hell. -Mark -- http://mail.python.org/mailman/listinfo/python-list
Re: Tracking down DLL load errors in Windows ?
Fred P xne...@fredp.lautre.net wrote in message news:xns9ca5e52bec783pacmanr...@212.27.60.39... Hi, a bit of platform-specific advice sought here... I'm trying to diagnose one of those mysteries Windows is so fond of... Say that I have code that imports some binary Python module from site- packages (in this case, libpyexiv2.pyd through pyexiv2.py, could be anythng else). On three Windows boxes I've tried it (XP Pro or Home, Python 2.5) everything works fine. On a fourth, importing the module fails with a traceback like this : Traceback (most recent call last): File stdin, line 1, in module File c:\python\lib\site-packages\pyexiv2.py, line 60, in module import libpyexiv2 ImportError: DLL load failed: This application could not start because its configuration is incorrect. Reinstalling it might solve the problem. I have tried long and hard to spot a meaningful difference between the first three systems and the last, without success. Is there any tool and/or methodology I could use to at least pinpoint the exact DLL that libpyexiv2 is failing to load, and ideally also the reason why ?... That error message is returned from executables built with later versions of Visual Studio (at least 2005 and 2008...not sure about 2003). The Windows application event log will indicate what DLL is missing. In addition to tools others have noted, depends.exe (comes with VS2005...was removed in VS2008 for unknown reasons) will list the DLLs required by an executable. Another Visual Studio tool, dumpbin /imports target works, too. -Mark -- http://mail.python.org/mailman/listinfo/python-list
Re: Tracking down DLL load errors in Windows ?
Christian Heimes li...@cheimes.de said : Fred P wrote: Is there any tool and/or methodology I could use to at least pinpoint the exact DLL that libpyexiv2 is failing to load, and ideally also the reason why ?... The depencency walker http://www.dependencywalker.com/ works fine for me. I'd never heard of that tool before, but it looks powerful indeed ! Thanks a lot for the pointer, fp -- http://mail.python.org/mailman/listinfo/python-list
Re: Tracking down DLL load errors in Windows ?
Fred P wrote: Is there any tool and/or methodology I could use to at least pinpoint the exact DLL that libpyexiv2 is failing to load, and ideally also the reason why ?... The depencency walker http://www.dependencywalker.com/ works fine for me. Christian -- http://mail.python.org/mailman/listinfo/python-list
