Static analysis, test coverage, and other 12+ letter words
Formal Metadata
| Title | Static analysis, test coverage, and other 12+ letter words |
|
| Subtitle | A tour of ways to find and prevent bugs in PostgreSQL |
|
| Title of Series | |
| Number of Parts | 31 |
| Author | |
| Contributors | |
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Ottawa, Canada |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | It is hard to maintain complex C code free of bugs. Numerous tools have been developed to help, and we have thrown many of them at the PostgreSQL source code.
We will take a look at tools such as
Coverity
Clang scan-build
AddressSanitizer
Valgrind
Gcov
How do they work? How should their results be interpreted? What have they and have they not delivered for us in practice? How can we integrate them into our workflow going forward? How can we structure our code better to work with tools like these? |
|
