--PGPMime-Boundary-4AD68A0F
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Content-description: Mail message body

On 23 Oct 2003 at 12:56, Raoul Gough wrote:

>  When I build the Python tests with MSVC (7.1 beta, version 13.10.2292)
>  I get non-functioning DLLs. With a debug build, importing an extension
>  module into Python aborts silently, and with the release builds it
>  reports "ImportError: DLL load failed: Invalid access to memory
>  location." I'm reasonably sure this was working a couple of weeks ago.
>  
>  I can report more details if necessary, but maybe somebody already has
>  experience with this happening? A sample link and test run follows
>  (lines manually wrapped). I'm using the indexing_v2 branch in
>  boost/python/suite/indexing and libs/python, and the CVS head
>  everywhere else. The problem occurs with the new indexing tests and
>  the existing tests I've tried as well (e.g. crossmod_exception.py).

I can tell you it works here fine too, though I have a CVS version 
from about two weeks ago and I have BPL as a static library. And my 
wrappers are so big they break MSVC if you include any debug info at 
all!

Try enabling kernel loader snaps - these will tell you where it's 
faulting. Find an article on MSDN by Matt Pietrek - ignore all that 
modern crap in MSDN, it's a 1996 or thereabouts article which 
typically MS have expunged from the latest MSDN's with MSVC7.1 :(

Cheers,
Niall




--PGPMime-Boundary-4AD68A0F
Content-Type: application/pgp-signature

-----BEGIN PGP MESSAGE-----
Version: idw's PGP-Frontend 4.9.6.1 / 9-2003 + PGP 8.0.2

iQA/AwUBP5gVtMEcvDLFGKbPEQI/2QCgyHtLw/cbw+6zJdRSeXD/jIFswxwAoN6u
o+iDkkDKh7nsuB2zJVgaNqq9
=dPIb
-----END PGP MESSAGE-----
--PGPMime-Boundary-4AD68A0F--