From: "Theo de Raadt" <deraadt@openbsd.org>
Subject: Re: follow up on 'stacktrace_save_utrace() should be more robust'
To: Alexandr Nedvedicky <sashan@fastmail.net>
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, tech@openbsd.org, tedu@tedunangst.com
Date: Mon, 09 Jun 2025 07:40:57 -0600

    My concern is cost. because to find invalid address is
    syscall + uvm_map_lookup_entry(). and we do it for every
    invalid return address found on stack. So if there is some
    way to find/determine invalid return on the stack then this
    will be more than welcomed.

Well, you could learn what ALL the text segments of the binary are.
For dlopen, you can learn them on the fly, later on.