bug-commoncpp
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Cplusplus-devel]CommonC++(TCPStream) Question


From: Federico Montesino Pouzols
Subject: Re: [Cplusplus-devel]CommonC++(TCPStream) Question
Date: Tue, 4 Sep 2001 14:30:16 +0200

        Hello again,

        Tracing the example that throws exceptions (with no telnet
server there), when the TCPStream constructor throws the expected
exception, instead of executing the catch block, the following
happens:


binding for: 127.0.0.1:23

Program received signal SIGABRT, Aborted.
0x401de3e1 in kill () from /lib/libc.so.6
(gdb) bt
#0  0x401de3e1 in kill () from /lib/libc.so.6
#1  0x401a4b2e in pthread_kill () from /lib/libpthread.so.0
#2  0x401a4ffd in raise () from /lib/libpthread.so.0
#3  0x401df841 in abort () from /lib/libc.so.6
#4  0x401513a8 in __terminate () from /usr/lib/libstdc++-libc6.2-2.so.3
#5  0x401513c5 in __terminate () from /usr/lib/libstdc++-libc6.2-2.so.3
#6  0x40151dc0 in __unwinding_cleanup () from /usr/lib/libstdc++-libc6.2-2.so.3
#7  0x40151f75 in __throw () from /usr/lib/libstdc++-libc6.2-2.so.3
#8  0x4003924c in cc_Socket::Error (this=0xbffff530,
    err=SOCKET_CONNECT_REFUSED, errs=0x0) at socket.cpp:312
#9  0x400391ed in cc_Socket::connectError (this=0xbffff530) at socket.cpp:293
#10 0x4003a65e in cc_TCPStream::Connect (this=0xbffff530, address@hidden,
    port=23, size=512) at socket.cpp:906
#11 0x4003a4d1 in cc_TCPStream::cc_TCPStream (this=0xbffff530, __in_chrg=1,
    address@hidden, port=23, size=512, throwflag=false, to=0)
    at socket.cpp:886
#12 0x08048e45 in main (argc=1, argv=0xbffffa94) at tcpstream-exc.cpp:16
#13 0x401ce46b in __libc_start_main () from /lib/libc.so.6


    (Linux 2.4.9, Debian unstable/testing, gcc 3.0.1)


    Everything seems to go well until socket.cpp:312, where there is a
line saying `throw((Socket *)this)', that I supposed should lead us to
the catch block. But terminate() is called, as if there were no catch
at all. (I have tried also with catch(...), just in case).

    Has anyone any idea of what is happening here or has experienced
something similar?

    Read you later.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]