Re: Oops stack trace missing function addresses

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: pgpQxFyOMA3OF.pgp
Description: PGP signature

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]

  Powered by Linux