Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

You'd normally use a library that hooks the exception throwing mechanism in the runtime library in a toolset-specific way.


Yes, but I mean that every exception will have an additional cost then, because you will have to copy the stack trace (implicitly or explicitly).


For many common ABIs, unwinding the stack is relatively cheap compared to decoding the debug info to figure out how to unwind the stack. If you have frame pointers, it's especially cheap -- you're walking a 20 element linked list.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: