You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 13, 2023. It is now read-only.
The kernel heavily relies on pointers to implement the equivalent of virtual functions, either by assigning a pointer directly in an initialization function or designated initializer, or for instance by setting a constant file_ops. All these assignments are against statically known functions or instances.
When such a static assignment to a pointer is performed, it would be great to be able to track the possible values the pointer takes and to display them to the user when such a pointer is highlighted. Since we are aware of the code that is actually needed by the kernel and only include necessary files, this should resolve to a reasonnable number of possibilities and be quite helpful to browse through code.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The kernel heavily relies on pointers to implement the equivalent of virtual functions, either by assigning a pointer directly in an initialization function or designated initializer, or for instance by setting a constant file_ops. All these assignments are against statically known functions or instances.
When such a static assignment to a pointer is performed, it would be great to be able to track the possible values the pointer takes and to display them to the user when such a pointer is highlighted. Since we are aware of the code that is actually needed by the kernel and only include necessary files, this should resolve to a reasonnable number of possibilities and be quite helpful to browse through code.
The text was updated successfully, but these errors were encountered: