Actually, I am compiling a very simple c program test.c with
gcc -g test.c -o test
but it is not affecting output. Is there any way by which I can check
whether the binary image generates debug info or not?
On Fri, Mar 24, 2017 at 3:26 PM, Michael Petlan wrote:
> Please read my previous messag
Hi,
Yes, when I try to execute 'opreport --symbols --debug-info' command after
doing profiling for a .c file (let operf ./test),
I am expecting 'test.c:line_no' in linear info field as you are getting
'exact_counts.c:13' in the following:
samples %linenr info image name
On Thu, 23 Mar 2017, dhara buch wrote:
Hello,
I am doing profiling with command,
operf ./test --events=BR_INST_RETIRED
where test.c is a simple c language file.
then, I am trying to collect information with command
opreport --symbols --debug-info
From the documents of Oprofile, I assume th