[ python-Bugs-1733134 ] sqlite3.dll cannot be relocated

[SourceForge.net]

Bugs item #1733134, was opened at 2007-06-08 01:15
Message generated for change (Comment added) made by loewis
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1733134&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Windows
Group: Python 2.5
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tim Delaney (tcdelaney)
Assigned to: Nobody/Anonymous (nobody)
Summary: sqlite3.dll cannot be relocated

Initial Comment:
>From Josh Ritter:

A number of our Windows customers have an issue with the sqlite3
module included with Python 2.5.1

We've tracked the problem down to the sqlite3.dll included with the
Python 2.5.1 distribition.  It is stripped and thus cannot be relocated.
This causes the following exception on computers where something is
already loaded into the address the sqlite3.dll wants to use:

File "sqlite3\__init__.pyc", line 24, in <module>
File "sqlite3\dbapi2.pyc", line 27, in <module>
ImportError: DLL load failed: Invalid access to memory location.

I downloaded the latest sqlite3.dll from http://www.sqlite.org and
this fixes the problem.  (This dll isn't stripped)

----------------------------------------------------------------------

>Comment By: Martin v. Löwis (loewis)
Date: 2007-06-08 19:49

Message:
Logged In: YES 
user_id=21627
Originator: NO

I don't understand the problem, either. There is no "strip" operation on
Windows that could cause this problem; relocation information is always
present and cannot be removed under normal circumstances. So I think the
problem is elsewhere.

If Josh Ritter could report what precisely he did to determine that the
2.5-shipped version was "stripped" and the sqlite.org version isn't, that
would be helpful.

According to http://support.microsoft.com/kb/q196069/
the error 998 of LoadLibrary indicates ERROR_NOACCESS if an access
violation occurred, 
so that might be a possible cause. To analyze this further, one would have
to run
the application under a debugger.

----------------------------------------------------------------------

Comment By: Gerhard Häring (ghaering)
Date: 2007-06-08 10:13

Message:
Logged In: YES 
user_id=163326
Originator: NO

Unfortunately, I don't know where the problem originates. Either the
SQLite 3.3.4 DLL that was originally imported into Python was stripped and
current ones aren't. Or somewhere in the Python win32 build process DLLs
are stripped.

Maybe we should just update the SQLite3.DLL to a current one in the Python
2.5 branch. Due to their extensive regression tests new ones should
generally be better than old ones. And the current SQLite DLL is too old
for some cases (SQLAlchemy refuses to work with it because it's too old and
buggy, for example).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1733134&group_id=5470