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
If you set a break-point on the same address numerous times the python process crashes. This happens e.g. when you set a bp from a callback function:
addr_1 = 0x...
addr_2 = 0x...
def cb_1(): print('1')
def cb_2():
with vm.break_on_physical(addr_1, cb_1)
...
with vm.break_on_physical(addr_2, cb_2)
...
# guest is calling addr_2 and addr_1 fiercely
The solution is rather obvious - one must keep track of addresses that already have a bp set and prevent duplicate bps. However, I thought SIGSEGV is not intended behavior so I did a little investigation.
Long story short, the buffer in struct Worker gets overflown and the co_thread pointer gets malformed. A following call to co_switch is going to kill the python process.
The text was updated successfully, but these errors were encountered:
If you set a break-point on the same address numerous times the python process crashes. This happens e.g. when you set a bp from a callback function:
The solution is rather obvious - one must keep track of addresses that already have a bp set and prevent duplicate bps. However, I thought SIGSEGV is not intended behavior so I did a little investigation.
Long story short, the buffer in
struct Worker
gets overflown and theco_thread
pointer gets malformed. A following call toco_switch
is going to kill the python process.The text was updated successfully, but these errors were encountered: