|
From: Julian S. <js...@ac...> - 2007-02-16 15:47:02
|
Hi Ashley > I've still got a couple of shared libraries where valgrind isn't > reporting functions/line numbers correctly for errors, what are the > instructions for using this new feature and I'll try it here, I remember > something about being able to enable it on a per so basis? Well, it's still in development. I just stopped for lunch and intend to chase some discrepancies it found now. Nevertheless: decide which so's you want to dump info for. Then do "--trace-symtab-patt=<pattern that matches the soname>" --debug-dump=frames and compare the results against readelf --debug-dump=frames for the .so in question. It's not pretty. I presume you are talking about amd64-linux here. --debug-dump=line works much better right now. If you can find any object where the readelf and valgrind outputs differ, I'd be interested to see it. > Incidentally --debug-dump=lines is giving a error although > --debug-dump=frames seems to work. Yes, I mistyped: it's --debug-dump=line. J |