https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71890
Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> --- I don't think this is a valid thing to do with setjmp and longjmp. Why are you not using makecontext/setcontext/getcontext/swapcontext instead? Also why do you think this is a libgcc bug because if you try to unwind the stack using gdb, you will get the same behavior because the stack was that one thread is now on the other one but the that thread has now exited.