Skip to content
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

[RFE] Print tracee's stack when ASSERT() fails #3749

Open
Hi-Angel opened this issue May 21, 2024 · 1 comment
Open

[RFE] Print tracee's stack when ASSERT() fails #3749

Hi-Angel opened this issue May 21, 2024 · 1 comment

Comments

@Hi-Angel
Copy link
Contributor

I am currently debugging an instance of

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.

@Hi-Angel
Copy link
Contributor Author

Hi-Angel commented May 21, 2024

(for reference: the assert per se comes from lack of libaio wrapper in rr, and there is a separate issue for that #3034)

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

No branches or pull requests

1 participant