clients(which I have made).
these.
means it will send the messages received from X to Y and from Y to X.
"Joseph M. Newcomer" wrote:
This code is neither interesting nor informative. You need to show YOUR code! You are
clearly triggering a valid error situation, but unless we see what you did, we have no way
to suggest how to fix it!
I have no idea what the nonsensical statement "everything works fine under Release build"
means, but what it almost certainly translates as is "my program is still broken in the
Release version, but it doesn't bother to tell me that it is malfunctioning because the
ASSERT statements are not compiled in Release versions". You have made the classic error,
thinking that absence of an error message means absence of an error. There's a *reason*
that the debug build fails: your program is wrong. The difference between debug and
release builds is that the release build doesn't bother to tell you that you screwed up.
NEVER play the "it works in Release mode" card until you have proven that it is not broken
in debug mode, and the ASSERT statement clearly tells you that your code is broken. The
"it works in release mode" rationale pretty much indicates that you haven't a clue that
your program really, truly, is broken. We sometimes call it the "ostrich approach" to bug
fixes (if I can't see the bug, it isn't there).
But since you simply duplicated a piece of code we all can see, without showing any of
your code (which is clearly wrong), we can't tell you how to fix it.
joe
On Sat, 25 Apr 2009 06:21:01 -0700, nexolite <nexolite@discussions.microsoft.com> wrote:
I have a CAsyncSocket which listens on some port .if a single connection is
made to it everything is fine ,now if one more Client attempts to connects
then the following Assertion fails
in sockcore.cpp
BOOL CAsyncSocket::Accept(CAsyncSocket& rConnectedSocket,
SOCKADDR* lpSockAddr, int* lpSockAddrLen)
{
ASSERT(rConnectedSocket.m_hSocket == INVALID_SOCKET);
....
}
Although everything works fine under Release build but I want to know is
that a concern?
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm