[Buildbot-devel] Problem with dnotify.py on AMD64

Jeff Pitman symbiont at berlios.de
Thu Sep 29 12:16:57 UTC 2005

On Thursday 29 September 2005 20:00, Brad Hards wrote:
> So I tried it without the fnctl.DN_MULTISHOT flag (0x80000000), and
> it appears to work (correctly - each time I make a change, the
> unittest flags it).

Strange.  You might have to peel away more layers and peer deeper in to 
see where the root of the problem is.  32-bit max is 0xFFFFFFFF, but 
that's unsigned.  If flags is signed, then the 32-bit max is 
0x80000000.  So, on a 32-bit signed integer: 0x8000001e is probably 
negative and fits the bill with a  (foo < max_signed_int) check.  On a 
64-bit system 0x8000001e in a signed integer is probably still 

I might be smoking something, but I think you either found a bug in 
python or in glibc.  Peel it apart, find out where that Overflow is 
coming from.  Is it from glibc and python is just forwarding it up?  Or 
is the check done in the wrapper code?  

Either way, getting a fix pushed out is going to take some time. (Time 
for hackery in dnotify??)


More information about the devel mailing list