edef

@RalfJung > The reason for this is quite simple: It should not be possible for a safe client (i.e., a client not using the unsafe keyword) to cause crashes using...

Can you reproduce this with current master? We're fixing a bunch of plumbing issues and unsafety that got into `1.x` right now, and I'm working on releasing `2.0.0` soon.

Okay, can reproduce with the branch I'm working on. Welp.

After spending a while in confusion, I've figured out what's up: ``` (rr) x/2i $pc-1 0x5619a1b72a20 : jmp 0x5619a1b72a22 0x5619a1b72a22 : nop ``` I'm not sure how this `jmp` is...

The tests are passing because we build them with optimisations, causing rustc to eliminate the extra `jmp`. I can either do an awful workaround, or I can wait for this...

@whitequark already did that, but there's more broken stuff (unwinding doesn't find a landing pad) - though maybe I can solve that with even more nops? Either way, fixing this...

@carllerche Yes, the main blocker is uncertainty about how this can be made to work well with `-C panic=abort`.

That's an exciting project! I'm afraid that getting libfringe to work on stable Rust would require stabilising inline assembly, though there are alternative (slower) approaches that could be implemented with...

If you already have a fork, send a pull request!

Is there an intention to allow adopting a bridge identity that has otherwise not interacted with the particular repository? This comment is partially a way of allowing me to adopt...