`udiv_bitvec` does not check for a second operand of `0` about boolector

[aniemetz]

@andrewvaughanj Good catch!

The issue here is indeed the udiv function in testbv.c, which obviously must use UINT64_MAX since the types are uint64_t. Good question why this came up with Windows, but not with Linux. In theory, rand() should return 0 on occasion, but very rarely so, probably. So yes, maybe it is less random on Windows?

I fixed the tests a bit differently than you suggested.
Can you check if you still encounter problems with f689fbb?

[aytey]

@aniemetz thanks for taking a look!

Everything now looks good to me (the important thing was the UINT32_MAX change):

Finished 1300 tests:
  Number of tests skipped: 19
  Number of tests succeeded: 1281
  Number of files successfully compared: 775/775

[aniemetz]

Great! Thanks for checking!