CygWin .pyd oddities
Matthew Turk
m-turk at nwu.edu
Tue Aug 21 12:00:06 EDT 2001
More information about the Python-list mailing list
Tue Aug 21 12:00:06 EDT 2001
- Previous message (by thread): CygWin .pyd oddities
- Next message (by thread): PyQt binary for Windows....but?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi there. I've been working on converting some of the more math-intensive operations to C from a python script; and after some trial and error (err, a LOT of trial and error) I have been able to make a callable extension using CygWin. I can use it fairly easily under Windows (there was a bit of a problem with the feof() macro apparantly not working, so I added a || to the statement to check for a char==-1) but now for some reason it has been taking issue with my memory management. I'm using a GPL'ed block allocater called blalloc which worked *perfectly* under cygwin. Upon transferring to W95, however, as near as I can trace it the extension crashes in a free() statement that I don't think it should. (It doesn't crash immediately; not until near the end of the program does it go down in flames.) All of this is pretty irrelevant (unless there's a malloc() difference I ought to know about!) - I would like to know if there's a method of debugging a C extension in python. Thanks! mjt -------------------------------------------------- Matthew J. Turk <m-turk at nwu.edu> ICQ: 3856787 "Music is the Best." - FZ www.dailyvault.com
- Previous message (by thread): CygWin .pyd oddities
- Next message (by thread): PyQt binary for Windows....but?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list