Bug in win32all-128 with multiprocessor NT
Mark Hammond
mhammond at skippinet.com.au
Thu Feb 24 19:35:44 EST 2000
More information about the Python-list mailing list
Thu Feb 24 19:35:44 EST 2000
- Previous message (by thread): Bug in win32all-128 with multiprocessor NT
- Next message (by thread): Bug in win32all-128 with multiprocessor NT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
<krodgers at tdyryan.com> wrote in message news:8947n9$c5k$1 at nnrp1.deja.com... > Here's a bug I've run across in win32all-128 (actually, has been present > at least since win32all-125, but I've been too busy to report it) on a > two-processor NT box. I can get it on an SP box :-) Pity you didnt report it - it would be history by now :-( The problem appears to be related to the optimizer - it did not happen in debug builds, and adding debug information to the release builds showed something very strange - I didnt dig to the assembly level, just disabled the optimizer for that SetProcessAffinity(), and it all started working again. This will be in 129. Mark.
- Previous message (by thread): Bug in win32all-128 with multiprocessor NT
- Next message (by thread): Bug in win32all-128 with multiprocessor NT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list