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
Make it possible to put a breakpoint on the base instruction instead of the explicit opcode (which is essentially the only possible way today, via watchpoints), so that one can break on any ROXL for example, regardless of its parameters.
This can (mostly) be done by using the actual function pointer value as the breakpoint trigger, because it's usually a generic dispatcher for the entire instruction handler.
The text was updated successfully, but these errors were encountered:
Make it possible to put a breakpoint on the base instruction instead of the explicit opcode (which is essentially the only possible way today, via watchpoints), so that one can break on any ROXL for example, regardless of its parameters.
This can (mostly) be done by using the actual function pointer value as the breakpoint trigger, because it's usually a generic dispatcher for the entire instruction handler.
The text was updated successfully, but these errors were encountered: