Thomas Wouters wrote: > On 3/9/06, Thomas Heller <[EMAIL PROTECTED]> wrote: >> ctypes is in SVN now, and the buildbot is green, > > > Well, only by accident; Neal's amd64 machine has been offline, or you would > have seen yellow blocks for warnings: ctypes has yet to be Py_ssize_t'ed. Do
Do compiler warnings create yellow blocks? There are other warnings on other machines as well. OTOH, testing ctypes (see below) can cause core dumps, these should create orange blinking blocks ;-) > you want to do that yourself, or do you want me to submit a patch? (Or I > could just check it in ;) You can do it faster then me, I assume - so go ahead and check it in. I'll backport it to the upstream ctypes CVS repository. >> after I disabled a test that dumped coreon sparc solaris. The crash was >> apparently caused >> > > Ohh, mystery. Do we get to guess what it was apparently caused by? :) It was caused by a test that did access misaligned integer fields in a structure. ctypes isn't yet able to handle this, but probably should steal the code for it from the struct module. But the change is not trivial I fear because of the access macros that also handle bit fields in structures. And I never had tried it before on a sparc machine - all the intel and ppc processors seem to have no problems with it. Thomas _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
