[Vortex] How to correctly close a connection?

Robert M. Münch robert.muench at robertmuench.de
Fri Oct 10 18:37:56 CEST 2008

Am 07.10.2008, 11:22 Uhr, schrieb Francis Brosnan Blazquez <francis at aspl.es>:

> Another check to do is to run your server using valgrind:
> libtool --mode=execute valgrind --db-attach=yes YOUR-SERVER.
> It will spot when and where was deallocated the memory wrongly accessed.

Hi Francis, so I did. Here is the log output:

==15524== Thread 2:
==15524== Invalid free() / delete / delete[]
==15524==    at 0x401D43C: free (vg_replace_malloc.c:323)
==15524==    by 0x45DF60C: axl_hash_free (axl_hash.c:1216)
==15524==    by 0x45B18F7: vortex_hash_destroy (vortex_hash.c:357)
==15524==    by 0x459ADF0: vortex_connection_free (vortex_connection.c:2494)
==15524==    by 0x45AFD60: __vortex_reader_build_set_to_watch_aux (vortex_reader.c:971)
==15524==    by 0x45B100C: __vortex_reader_run (vortex_reader.c:1228)
==15524==    by 0x460823F: start_thread (in /lib/tls/i686/cmov/libpthread-2.3.6.so)
==15524==    by 0x411A49D: clone (in /lib/tls/i686/cmov/libc-2.3.6.so)
==15524==  Address 0x45e72f8 is not stack'd, malloc'd or (recently) free'd

Any idea?

Robert M. Münch
Mobile: +49 (177) 245 2802

More information about the Vortex mailing list