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
ExecBrocker allows any users to remove code ranges from the scope of QBDI, letting the program execute freely when jumping outside of it.
It currently only implement one strategy to get the execution back, which works well for generic cases (classic external call to a library). But when it gives up, there is currently no way to fix its behavior.
A new user API should be added, in order to provide ways to customize how QBDI is getting control back.
The text was updated successfully, but these errors were encountered:
ExecBrocker allows any users to remove code ranges from the scope of QBDI, letting the program execute freely when jumping outside of it.
It currently only implement one strategy to get the execution back, which works well for generic cases (classic external call to a library). But when it gives up, there is currently no way to fix its behavior.
A new user API should be added, in order to provide ways to customize how QBDI is getting control back.
The text was updated successfully, but these errors were encountered: