I havean applicationbuilt using2 shared libraries. The associated *.dyn files related to these2 shared libraries are generated in2 separate directories, when application is executed. When I create a pgopti.dpi file after putting all *.dyn files related to2 shared librariesin a single directory and then create a coverage report out of it, it gives me coverage information about source files present in only one shared library. So I lose all the coverage information for otherlibrary.
If I createpgopti.dpi files related toeach library, and merge pgopti.dpi files with profmerge -a, and then create coverage report then also I end up with coverage information about same single library.
If I create pgopti.dpi file from *.dyn files related to other library and generate coverage report then I could get coverage information forother library correctly.
Please let me know, is this a known issue with profmerge tool, and how could I resolve this.
Thanks in advance.
Pleasenote thatthe primary information that drives the code coverage report comes from the pgopti.spi file. If you are targeting your shared objects to different directories using the prof-dir option with prof-gen:srcpos, then you are also producing 2 different pgopti.spi files. As a result, even if all the .dyn data is merged into a single .dpi file, the information contained in the coverage report is only going to be about the files/routines that are listed in whichever pgopti.spi that gets loaded. So, I would check whether this is the scenario that you have different pgopti.spi files for the different shared objects.
Please also note that there is notcurrently a way to merge pgopti.spi files.