Re: CAsyncSocket Assertion When Terminating
- From: Joseph M. Newcomer <newcomer@xxxxxxxxxxxx>
- Date: Thu, 26 Apr 2007 13:47:04 -0400
As far as the last updated list from IANA, that port is unassigned (although it might
become assigned next week).
joe
On Wed, 25 Apr 2007 07:08:03 -0700, Joe <Joe@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Joseph M. Newcomer [MVP]
2001 is a poor choice of value for a port number, since it is already assigned to someone
else. Unless you have the alias 'curry' and have received this port assignment from IANA.
Check
http://www.iana.org/assignments/port-numbers
Hi Joe. Sorry, port 2001 won?t be my ?real? port number ? especially since
it?s just hardcoded in my sample code. I?m just using it as an example. The
real port number is defined in some constant, let?s see, It?s 8817.
Where is the Close with respect to other code. For example, do you call Close in the
OnDestroy handler of MyAppView? You have not provided anything like enough useful
information here to make sense of the problem.
joe
Yes, I as I stated in my original question, I tried to call Close() in my
OnDestroy(), and I also tried to not call Close() at all (and let the socket
close itself automatically), but. I still get the assertion. What other
information would be helpful? Unfortunately I don?t have the code on this
network, and I am required to re-type any code I have over here ? which I can
do, but I would need to know what other pieces of code would be useful.
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.
- References:
- Re: CAsyncSocket Assertion When Terminating
- From: Joseph M . Newcomer
- Re: CAsyncSocket Assertion When Terminating
- Prev by Date: Re: Display Bitmap using GDI+
- Next by Date: Re: CAsyncSocket Assertion When Terminating
- Previous by thread: Re: CAsyncSocket Assertion When Terminating
- Next by thread: Re: CAsyncSocket Assertion When Terminating
- Index(es):
Relevant Pages
|
