Need help concerning weird SIGABRT on socket timeout

[Viktor Lundström]

Hello!
I have a problem handling socket timeouts in a
subclass of TCPSession.
When I use a set timeout (using setTimeout(...) in
the constructor), and an I/O operation times out,
no exception is thrown, but instead the process receives
a SIGABRT signal, making it exit to prompt with the
message "Abort".

Other I/O errors such as unexpected eof successfully
throw exceptions (when iostream exception flags are set).

I've also tried this using TCPStream in a non-threaded
application and with the same results.

I'm using SunOS 5.8.

Any help would be appreciated.

/Viktor Lundström