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

glib: Internal error checking in closures and signal handlers should abort instead of panic #645

Closed
jf2048 opened this issue Apr 12, 2022 · 1 comment
Closed

glib: Internal error checking in closures and signal handlers should abort instead of panic #645

jf2048 opened this issue Apr 12, 2022 · 1 comment

Comments

@jf2048
Copy link
Member

jf2048 commented Apr 12, 2022

This is in places such as inside the callbacks in RustClosure and ObjectExt::try_connect_unsafe_id. A user will never be able to safely use catch_unwind on these because they always cross an FFI boundary.
@jf2048 jf2048 mentioned this issue Apr 12, 2022
Merged
@sdroege
Copy link
Member

sdroege commented Apr 12, 2022

See #74 . This will be solved once C-unwind is stabilized AFAIU

@sdroege sdroege closed this as completed Apr 12, 2022
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

No branches or pull requests
2 participants
@sdroege @jf2048