Fix uncaught exception crash when socket ready read signal throws

When the application (in this case, an autotest) ran out of memory by
calling readAll() in a slot, the exception propagated to the symbian
active scheduler where it caused an assertion failure.
Additionally, QAbstractSocket was left in a bad state because its
member variables that guard against re-entrancy were left set.

1. Catch exceptions and convert to leaves in QAsyncSelect
2. Implement RunError function to set the socket engine error state
3. Use QScopedValueRollback in QAbstractSocket to ensure the reentrancy
   guards are reverted if an exception is thrown.

Reviewed-by: Markus Goetz
Reviewed-by: mread

0 files changed, 0 insertions, 0 deletions