public inbox for linux-perf-users@vger.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: Internal error while annotating function
Date: Mon, 24 Feb 2025 16:11:22 -0800	[thread overview]
Message-ID: <Z70KqrJXaVcIq8qh@google.com> (raw)
In-Reply-To: <20250224-accurate-pigeon-of-adventure-386dcd@leitao>

Hello,

On Mon, Feb 24, 2025 at 08:05:57AM -0800, Breno Leitao wrote:
> Hello,
> 
> I am trying to run annotate a perf function on aarch64, and it returns
> an error. How do I get the logs for what is happening?
> 
> Here is what I see, in either `perf top` or `perf report`:
> 
> 1) Open the TUI
> 2) Get on top of a specific hot function. Not all of them reproduce the
>    error. For instance, one of these functions is `finish_task_switch`
> 3) Press "Annotate finish_task_switch"
> 4) Got the following error:
> 
> 	┌─Error:──────────────────────────────┐
> 	│Couldn't annotate finish_task_switch:│
> 	│Internal error: Invalid -1 error code│
> 	│                                     │
> 	│                                     │
> 	│Press any key...                     │
> 	└─────────────────────────────────────┘
> 
> At the bottom I also see:
> 
> 	Error running objdump  --start-address=0xffff800080907fa0 --stop-address=0xffff800080908220  -d --no-show-raw-insn -S      -C "$1"
> 
> If I try to run this manually, I see the following. Is this the real
> cause?
> 
> 	# objdump  --start-address=0xffff800080907fa0 --stop-address=0xffff800080908220  -d --no-show-raw-insn -S -C /boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da
> 
> 	objdump: /boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da: unknown type [0x13] section `.relr.dyn'
> 	objdump: /boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da: unknown type [0x13] section `.relr.dyn'
> 	/boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da:     file format elf64-little
> 	objdump: can't disassemble for architecture UNKNOWN!
> 
> The file seems to be a valid aarch64 binary:
> 
> 	$ file /boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da
> 	/boot/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da: symbolic link to /lib/modules/6.13.2-0_fbk0_rc8_0_g925d379822da/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da
> 	$ file /lib/modules/6.13.2-0_fbk0_rc8_0_g925d379822da/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da
> 	/lib/modules/6.13.2-0_fbk0_rc8_0_g925d379822da/vmlinux-6.13.2-0_fbk0_rc8_0_g925d379822da: ELF 64-bit LSB pie executable, ARM aarch64, version 1 (SYSV), statically linked, BuildID[sha1]=be549c9fd62405a10f6b36236610cd6a57a6d3e3, with debug_info, not stripped
> 
> Any clue how to investigate this further?

What's the version of binutils?  Is it old?  I don't know what's the
problem but checking the latest version might help.

Thanks,
Namhyung


  reply	other threads:[~2025-02-25  0:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 16:05 Internal error while annotating function Breno Leitao
2025-02-25  0:11 ` Namhyung Kim [this message]
2025-02-25 15:27   ` Breno Leitao

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Z70KqrJXaVcIq8qh@google.com \
    --to=namhyung@kernel.org \
    --cc=leitao@debian.org \
    --cc=linux-perf-users@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox