Created by: Carrotman42
As mentioned in the modified code comment, this call to signal_reinstate_handlers was not good:
- It was not necessary: the newly cloned thread already is sharing the signal handler table with the app's thread group
- Since DR only partially unregisters its signal handlers right before dr_app_setup() returns, it causes an application signal handler to receive signals (such as SIGSEGV) that DR expects to send to itself (e.g. during TLS) when an application thread receives a signal between dr_app_setup() and dr_app_start().
Issue: #2335 (closed)