> memory is executable code, but it behaves like
> other process memory such as the heap or the stack
> other process memory such as the heap or the stack
Seems like it is not a problem: with GNOME effect is the same as with other environments.
пн, 14 сент. 2020 г. в 21:14, Benjamin Berg <bberg@xxxxxxxxxx>:
On Mon, 2020-09-14 at 20:35 +0900, Alexey A. wrote:
>
> > may be different for GNOME with JIT'ed code
> > potentially getting swapped out
>
> How to recognize JIT'ed code? Do you mean that we shouldn't lock it?
I don't think you can protect it using your tool, as it lives in
anonymous mappings. If it is reclaimed it will be written to swap.
Said differently, that memory is executable code, but it behaves like
other process memory such as the heap or the stack.
Benjamin
_______________________________________________
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
_______________________________________________ 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
