Re: [gnet] cancelling async connections

[Hubert Sokołowski <H Sokolowski wsisiz edu pl>]

On Mon, 23 Feb 2004, Andreas Rottmann wrote:

> Just a general hint: try running valgrind
> (http://valgrind.kde.org/). Perhaps that gives you more insight.
Connecting to idi.tlen.pl:80...
==28991== valgrind's libpthread.so: IGNORED call to: pthread_attr_destroy
--- tlen_connection_close ---
Cancelling connection
==28991==
==28991== Invalid write of size 4
==28991==    at 0x4065A26B: gnet_tcp_socket_connect_inetaddr_cb
(tcp.c:124)
==28991==    by 0x406579FE: inetaddr_new_list_async_pthread_dispatch
(inetaddr.c:1199)
==28991==    by 0x4060D972: (within /usr/lib/libglib-2.0.so.0.200.3)
==28991==    by 0x4060ACFF: (within /usr/lib/libglib-2.0.so.0.200.3)
==28991==    Address 0x43471F08 is 8 bytes inside a block of size 28
free'd
==28991==    at 0x40029E8B: free (vg_replace_malloc.c:231)
==28991==    by 0x40610903: g_free (in /usr/lib/libglib-2.0.so.0.200.3)
==28991==    by 0x4065A439: gnet_tcp_socket_connect_async_cancel
(tcp.c:256)


this part repeats few times and connection is established, not canceled.

there are no examples in gnet sources of cancelling async connections. can
you give me some example? maybe I do something wrong. what happens after I
cancel connection? is the callback called after cancel?


regards
hs~