Closed jynik closed 10 years ago
I picked up a few more bugs when increasing scan-build's -maxloop option to 16. It looks like scan-build defaults to 4?
Perhaps the build-bot could run it with 100 if you want to get wild and crazy? It looks like 1000 causes it to take some time! :neckbeard:
This has been implemented! It takes about 8 minutes, which is fine. Interestingly, ezusb.c crashes it. It carries on, of course, but that's kind of amusing.
I picked up a few more bugs when increasing scan-build's -maxloop option to 16. It looks like scan-build defaults to 4?
Perhaps the build-bot could run it with 100 if you want to get wild and crazy? It looks like 1000 causes it to take some time! :neckbeard: