We have been addressed several times already with the question where one can see documentation on VivaCore library. Unfortunately, I must tell you that there is no documentation on VivaCore library at present.
VivaCore library is being developed as part of Viva64 and VivaMP tools. We are a small company and, unfortunately, don't possess enough resources to fully develop VivaCore library. Currently VivaCore library has no technical documentation.
If your company is interested in creating projects on the basis of VivaCore library, we can offer you three variants:
1) You can study documentation on OpenC++ (OpenCxx) library on the basis of which VivaCore library is built - http://opencxx.sourceforge.net/. VivaCore is a continuation of OpenC++ library's development and has an identical architecture. I want to warn you at once that documentation on OpenC++ is rather superficial too and may not be enough to start using its abilities quickly and fully. To get acquainted with VivaCore, we can offer only our article: http://www.viva64.com/art-2-2-449187005.html
2) Your company can order development of documentation on VivaCore library. Your company can also sponsor development of VivaCore library and in this case we will implement all the functional abilities you need in it.
3) It would be a good solution to give us the tasks of developing a specialized toolkit or a part of a tool you need. It will save time for your specialists won't have to go deep into the peculiarities of the library structure and study the questions relating to analysis/parsing of code. As a result, development of a toolkit by our specialists will be much cheaper than your specialists' work. Besides, we can provide a good quality at low costs as we are familiar with this sphere quite well.
I develop the PVS-Studio static code analyzer intended for analyzing C/C++ software. After we implemented general analysis in PVS-Studio 4.00, we received a lot of responses, both positive and negative. By the way, you are welcome to download a new version of PVS-Studio where we have fixed a lot of errors and defects thanks to users who told us about ...
As a PVS-Studio's developer, I am often asked to implement various new diagnostics in our tool. Many of these requests are based on users' experience of working with dynamic code analyzers, for example Valgrind. Unfortunately, it is usually impossible or hardly possible for us to implement such diagnostics. In this article, I'm going to explain briefly why static code analyzers ...