From derek.br...@gmail.com on August 11, 2009 01:18:30

We no longer block SUSPEND_SIGNAL (issue #184) or SIGSEGV (issue #193).
But we can have re-entrancy issues in this routine if the app uses the same
SUSPEND_SIGNAL, or the nested SIGSEGV needs to be sent to the app. The
latter shouldn't happen unless the app sends SIGSEGV via SYS_kill().
To avoid re-entrant execution of special_heap_alloc() and of
prepending to the pending list we just drop this signal.
This Issue covers supporting re-entrant recording.

Original issue: http://code.google.com/p/dynamorio/issues/detail?id=194