MySQL database management tool ScaleBase virtualizes MySQL database, spreading database load into smaller bite-size chunks As an open source company, Mozilla developers make a lot of different versions of software code each day, and part of Sheeri Cabral’s job to keep track of them all: which ones work, which don’t, how many times they’ve been downloaded, and which have a [...] Read More

Hi,

We are currently running code coverage for MySQL Cluster testing and have hit a few bumps along the road when it cam to collecting the "block" coverage for the NDBD.

I wanted to share them here for others that might run into similar frustrations when doing testing code coverage.

Gcov accumulates during each run information on which functions and lines of code are called and a total for the times called.

The problem comes from when gcov dumps this information out. The actual data is dumped on the "exit" of the program.

After much time tracking this issue down, it turns out that the NDBD code had been changed to use _exit() instead of just exit()

What is the difference?

exit()
Terminate the process after cleanup.

_exit()
Terminate process immediately.

So by calling _exit(), gcov never had a …