gcov support for shared library

[AKSHYA CHHABRA]

Ralf Wildenhues <Ralf.Wildenhues <at> gmx.de> writes:

> 
> Hello,
> 
> Neuberger, Daniel [USA] writes:
> 
> > You were absolutely, right.  Thanks so much for the help.  We're using
> autotools and it turns out that all of
> > the .gcda files were ending up in the .libs directory.  The script we 
were
> using to produce output from gcov
> > was finding them correctly, but since they weren't in the same directory 
as
> the source files, gcov didn't
> > produce any output.
> 
> Ah, thanks for this information.  You can pass --object-directory .libs
> to gcov to help it find the right .gcda files.
> 
> I'm wondering how autotools could help make this sort of processing easier 
or
> more automatic.  That would certainly be something I'd love to see 
included.
> 
> Thanks,
> Ralf
> 
> 



For me the .gcda files is itself not getting generated any where in my env. 
I hope I have not missed anything . I am working with shared libraries. Any 
pointer ???

for me the .gcno is generated properly after compilation and the .gcno and 
.so is in the same directory . The main process which I am running is 
loading this shared library and calling it for during various operations. 
With this main process I am doing those operations but somehow the .gcda is 
not getting generated because of which I am not able to run gocv on the 
source file.