Hi, I have a program that dlopens() a libxx.so, jumps into it, and continues the rest of the execution in it. libxx.so gets built with -Ttext-segment,0x20400000. The problem I am facing is that perf report is not showing the symbols in libxx.so.
I added an empty infinite loop at the beginning, in the entry-point function of libxx.so, so that all the cycles get spent in the entry-point function. When I use perf report to look the results of a perf record of the modified entry-point, report shows the correct offset of the infinite-loop jump instruction, from the start of libxx.so, but it does not associate it with the entry-point function name. I see that the entry-point function name is available, when I look at it using the mapfile viewing option provided inside perf report. If I remove the "-Ttext-segment,0x20400000" option, then perf report shows the entry-point function name correctly. All this leads me to believe that perf record is correctly able to identify the libxx.so .text start address, allowing it to report offsets correctly. But perf report somehow is not able to figure out the .text start address of libxx.so. Is this correct ? If so, how do I get perf report to figure out the correct start address for libxx.so ? Thanks. Karthik -- To unsubscribe from this list: send the line "unsubscribe linux-perf-users" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
