Debug info for panic in FFI

[antoyo]

Hi.
I had a lot of trouble to debug this issue, so instead of just having "Uncaught panic, exiting", it would be nice to have more info maybe the stack trace, to be able to debug.
Thanks.

[EPashkin]

This not under gir control, see https://github.com/gtk-rs/glib/blob/master/src/source.rs#L75-L85

[antoyo]

I know this message comes from this code, but perhaps gir could generate code using catch_unwind() or something.
Or perhaps in the code you mentioned we should get the stack trace in the condition using libbacktrace.

[EPashkin]

Need of CallbackGuard will be removed in 1-2 rust stable release,
as rust will be do it yourself, then I hope RUST_BACKTRACE will works as usual.
See end of #250.

[EPashkin]

@antoyo As you have panic test case, can you check that panic will be caught without this line https://github.com/gtk-rs/gio/blob/master/src/auto/socket_listener.rs#L99 and that RUST_BACKTRACE=1 works as usual ?

[EPashkin]

I mean that unwinding already landed in last stable (second time), we just waiting to be sure that it will be not reverted again.

[antoyo]

Yeah, I see the backtrace on Rust nightly.

[EPashkin]

Thanks for confirming, so we just wait for stable 1.26.0 and remove CallbackGuard again

[sdroege]

I mean that unwinding already landed in last stable (second time)

It was not ready for 1.25 unfortunately

[EPashkin]

Then we better wait for stable 1.27.0