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
Assertion `t->regs().syscall_result_signed() == -syscall_state.expect_errno' failed to hold. Expected ENOSYS for 'io_destroy' but got result -22 (errno EINVAL); execution of syscall unsupported by rr
and the first thing I struggle with is that I have no idea where exactly rr fails. syscalls are typically hidden under 3rdparty libs, in particular I found that the io_destroy from this error message is wrapped over by io_queue_release, so I can't grep over the project for io_destroy.
I think it would be an immense help if in ASSERT() along with the internal trace rr would print the debuggee's stack as well.
The text was updated successfully, but these errors were encountered:
I am currently debugging an instance of
and the first thing I struggle with is that I have no idea where exactly
rr
fails. syscalls are typically hidden under 3rdparty libs, in particular I found that theio_destroy
from this error message is wrapped over byio_queue_release
, so I can't grep over the project forio_destroy
.I think it would be an immense help if in
ASSERT()
along with the internal tracerr
would print the debuggee's stack as well.The text was updated successfully, but these errors were encountered: