Re: [Opentnl-general] Aborting Connection Attempt

[Marc R. <mar...@ud...>]

Hi !
 
What I do is creating the MyNetInterface, then a MyNetConnection and call
Connect on the later one, giving the NetInterface as a parameter.
MyNetConnection is 512 bytes in size and that's the size of the block that
doesn't get freed - so I guess that's the trouble maker. Do I have to call
delete on that manually at some point? I create it with new but I never
delete it myself. Maybe in that case I have to? If the connection
establishes successfully and I do a disconnect, nothing leaks - while I'm
still not deleting the MyNetConnection I created before.
 
Best regards
   Marc

  _____  

Von: ope...@li...
[mailto:ope...@li...] Im Auftrag von Mark
Frohnmayer
Gesendet: Donnerstag, 27. März 2008 01:06
An: ope...@li...
Betreff: Re: [Opentnl-general] Aborting Connection Attempt


I think disconnect() will do it -- do you have info on which allocation is
not being deallocated correctly?


On Wed, Mar 26, 2008 at 3:17 PM, Marc Rochel <mar...@ud...> wrote:


Hi !
 
How do I abort a connection attempt correctly? When I do a connect and try a
disconnect before 

onConnectionEstablished() was called, the vs memory debugger reports a
memory leak at the end of the program. Like the NetConnection wasn't freed
correctly. What do I have to call instead? I don't seen any
abortConnectionAttempt() etc.

Best regards

    Marc


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Opentnl-general mailing list
Ope...@li...
https://lists.sourceforge.net/lists/listinfo/opentnl-general