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.

Sign up for GitHub

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

Jump to bottom

Safe FFI boundary #40

Closed
bazhenov opened this issue Jan 3, 2025 · 0 comments · Fixed by #41
Closed

Safe FFI boundary #40

bazhenov opened this issue Jan 3, 2025 · 0 comments · Fixed by #41

Comments

@bazhenov
Copy link
Owner

bazhenov commented Jan 3, 2025 •
edited
Loading

When panic occurs in testing function it's an UB, because stack unwind should never cross FFI boundary. Until we're using crABI all FFI calls should contain catch_unwind() and report errors probably via separate error function.
@bazhenov bazhenov mentioned this issue Jan 3, 2025
Merged
5 tasks
@bazhenov bazhenov closed this as completed Jan 5, 2025
@bazhenov bazhenov linked a pull request Jan 5, 2025 that will close this issue
Safe FFI boundary #41
Merged
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Safe FFI boundary bazhenov/tango
1 participant
@bazhenov