From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Adrian Larumbe <fromago@gmail.com>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>
Subject: Re: Oops stack trace missing function addresses
Date: Thu, 15 Oct 2020 23:52:46 -0400 [thread overview]
Message-ID: <260903.1602820366@turing-police> (raw)
In-Reply-To: <20201015173408.piqrtfpeik2rni36@arch-linux.localdomain>
[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]
On Thu, 15 Oct 2020 18:34:08 +0100, Adrian Larumbe said:
> claims, I get no VA next to each function in the Call Trace:
>
> Call Trace:
> do_one_initcall+0xfc/0x290
> ? cache_alloc_debugcheck_after+0x38/0x270
> ? rcu_read_lock_sched_held+0x77/0xa0
> ? kmem_cache_alloc_trace+0x2b6/0x330
> do_init_module+0x4b/0x1b6
> load_module+0x2140/0x24c0
OK, I'll bite. You *are* getting the function name and offset, what additional
knowledge do you get from knowing the VA?
What architecture is this on? Stack unwinding is architecture-dependent, so
it may just be the unwinder for that arch doesn't output the virtual address.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-10-16 3:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 17:34 Oops stack trace missing function addresses Adrian Larumbe
2020-10-16 3:52 ` Valdis Klētnieks [this message]
2020-10-16 11:49 ` Adrian Larumbe
2020-10-16 12:27 ` Alexander Kapshuk
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=260903.1602820366@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=fromago@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).