On 1/16/23 16:32, Daniel Colascione wrote: >> Could the vDSO do the unwinding? > > The vDSO is just userspace code that happens to be provided by the kernel, so, sure, a function in vDSO *could* unwind. But why would it? What would be the advantage of doing that over putting the unwinding in libc? To change the vDSO, you have to change the kernel, so the vDSO is more suited for things coupled to the kernel, like a fast clock_gettime implementation. Having the vDSO do the unwinding allows the unwinding to be entirely transparent to userspace programs and libraries, and therefore provides complete compatibility with the in-kernel unwinder. It also allows supporting programs in languages such as Go that do not use any libc.-- Sincerely, Demi Marie Obenour (she/her/hers) _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
