Changes between Version 83 and Version 84 of TracSubversion

Timestamp:

Sep 6, 2010, 2:42:00 PM (14 years ago)

Author:

Christian Boos

Comment:

add some debugging tricks for troubleshooting windows installation of the bindings

TracSubversion

@@ -43 +43 @@
 * Note: if !CollabNet is providing SWIG bindings for Python 2.6, I can't find them. In fact, since the move to apache.org, I can no longer find the 2.5 bindings.
 * Also note: the Subversion directory structure of the Algazam distro is slightly different than the !CollabNet one: all the executables are in the `bin` subdirectory.
+
+If you end up with the infamous //`ImportError: DLL load failed: ...`//, don't despair but have a look at the [#checklist-windows Windows troubleshooting] section below.
 
 === BSDs
@@ -255 +257 @@
  If you get the message {{{ImportError: libsvn_swig_py-1.so.0: cannot open shared object file: No such file or directory}}} even though you can see the .so file in the correct place, then try {{{ldconfig -v}}} as root.
 
- '''Windows Users'''
-
- According to the README.txt file for the Subversion bindings, if you are using Python 2.5+ you need to rename all the .dll files in the libsvn folder to .pyd files. Upon further research, http://www.python.org/doc/faq/windows/#is-a-pyd-file-the-same-as-a-dll indicates you may need to have both the .pyd and .dll version of the libsvn files available. This resolved both the 'ImportError: No module named _core' error (with only the DLL) and the 'ImportError: DLL load failed' (with only the pyd) when testing from the console, and the browswer.
+ '''Windows Users''' [=#checklist-windows]
+
+ According to the README.txt file for the Subversion bindings, if you are using Python 2.5+ you need to rename all the .dll files in the libsvn folder to .pyd files. Upon further research, http://www.python.org/doc/faq/windows/#is-a-pyd-file-the-same-as-a-dll indicates you may need to have both the .pyd and .dll version of the libsvn files available. This resolved both the '`ImportError: No module named _core`' error (with only the DLL) and the '`ImportError: DLL load failed`' (with only the pyd) when testing from the console, and the browser.
+
+ A good way to diagnose a //DLL load failed// error is to use the [http://www.dependencywalker.com/ depends.exe] tool from the console in which you'd run python.exe, and do a `depends.exe absolute-path-to/python.exe` instead. Then, press `F7` (//Start Profiling...// - you need at least version 2.0 of depends.exe) and type `from svn import core` at the Python prompt in the new cmd window. This will try to load the bindings, but this time you'll be able to see //why// this fails, by spotting the .DLLs shown in red in the Module list, and there are really lots of options here ;-)