10000 Don't attempt to patch inline cache entries if the block has none by WorksButNotTested · Pull Request #1033 · frida/frida-gum · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Don't attempt to patch inline cache entries if the block has none #1033

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 29, 2025

Conversation

WorksButNotTested
Copy link
Contributor

No description provided.

@oleavr
< 8000 div class=" timeline-comment-group js-minimizable-comment-group js-targetable-element TimelineItem-body my-0 " id="issuecomment-2917632991">
Copy link
Member
oleavr commented May 28, 2025

Thanks! Should gum_exec_block_backpatch_inline_cache() even be called for such blocks? I'm wondering if the root cause here is that we shouldn't be emitting a call to that function.

@WorksButNotTested
Copy link
Contributor Author

I think the root cause is a difference between the trust threshold at the point the block is prefetched between the parent and child in the forkserver. So the child creates the block with an online cache whilst the parent does not (at least initially).

Trying to track this externally seemed like exposing the consumer of the library to the internal implementation. Further having an external API which would perform a null dereference if called with invalid parameters seemed like a bad idea anyway.

@oleavr oleavr merged commit 4f0016e into frida:main May 29, 2025
33 of 44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0