On 26/08/09 15:13, Madhan Sadasivam wrote: > When intel compiler is used with profiler guided optimization, > two new sections called "text.hot" and "text.unlikely" are > created by the compiler. This is on Linux x86 32 bit. > > The symbols in these sections are not read by Valgrind > and this causes many frames in memcheck error stack traces > to be unresolved. > > Are there any ways to handle this.
Probably not without changing valgrind, no. We could just add these sections to the ones we process, but I think we've probably gone as far as we can down that road and adding yet more will just make the ELF core even more unreadable that it already is. We really need to rewrite things in a scalable way where we can track an arbitrary number of text and data sections. Tom -- Tom Hughes (t...@compton.nu) http://www.compton.nu/ ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
