You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run the program, I'd expect to see something like SIGSEGV received
on foreign thread, and then the process should exit (crash).
However, what you will actually see is that the process will print DONE
after 5 seconds and exit normally. But if you run the program under gdb,
you will see that thread is triggering SIGSEGV again and again.
The text was updated successfully, but these errors were encountered:
Instead, our sigtramp will simply return without modifying the ucontext, and
then the faulty code will trigger the same fault again, .....
http://play.golang.org/p/L1WXDwUFTf
If you run the program, I'd expect to see something like SIGSEGV received
on foreign thread, and then the process should exit (crash).
However, what you will actually see is that the process will print DONE
after 5 seconds and exit normally. But if you run the program under gdb,
you will see that thread is triggering SIGSEGV again and again.
The text was updated successfully, but these errors were encountered: