CL.exe problem with header - C / C++ / MFC Discussion Boards

Re: Sockets and resource limit per thread

Randor 8-May-08 8:51

Randor

8-May-08 8:51

There is a limit of 10,000 handles per process on Windows XP. I have no idea what the limit is on Vista. My guess is that you are reaching this limit.

Maximum NT User Handles Per Process Is 10,000 in Windows XP[^]

CreateIoCompletionPort consumes 1 handle as does each socket.

3956 * 2 = 7912

Not counting GDI/window and other types of handles.

You can try changing the registry key HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\USERProcessHandleQuota to check if my theory is correct. I may be wrong.

Best Wishes,
-David Delaune

Re: Sockets and resource limit per thread

bob169728-May-08 8:58

bob16972

8-May-08 8:58

I've seen that limit in action with too many windows, gdi related handles etc...

However, my IOCP server which is on the same box is handling more than 30,000 sockets.

Thanks for the idea.
Any other suggestions?

Re: Sockets and resource limit per thread

bob169728-May-08 10:03

bob16972

8-May-08 10:03

Just for kicks, since I found a few references to locked page limits and references that talked about increasing the working set, I gave this a try but no change in behavior...

HANDLE hProcess=GetCurrentProcess();
if (hProcess) {

DWORD dwMin, dwMax;
if (GetProcessWorkingSetSize(hProcess, &dwMin, &dwMax)) {

TRACE("Before\n");
TRACE("Minimum working set: %lu Kbytes\n", dwMin/1024);
TRACE("Maximum working set: %lu Kbytes\n", dwMax/1024);
}

SetProcessWorkingSetSize(hProcess, 204800, 1413120*4);

if (GetProcessWorkingSetSize(hProcess, &dwMin, &dwMax)) {

TRACE("After\n");
TRACE("Minimum working set: %lu Kbytes\n", dwMin/1024);
TRACE("Maximum working set: %lu Kbytes\n", dwMax/1024);
}
}

Re: Sockets and resource limit per thread

Randor 8-May-08 10:24

Randor

8-May-08 10:24

I don't think increasing the working set will have any effect. Based on what I have read you can implement zero-byte read operations to prevent exceeding the locked pages limit. I believe you should focus your attention to two areas:

1.) Non-Paged pool limit.
2.) Locked pages limit.

Here is a sample chapter from Network Programming for Microsoft® Windows®, Second Edition[^] which addresses the issue.

Best Wishes,
-David Delaune

Re: Sockets and resource limit per thread

bob169728-May-08 10:56

bob16972

8-May-08 10:56

Funny, thats the same article I've been digging through.

I agree. I've been trying to reduce my usage to see if that allows the connection limit to vary.

Thanks again for taking the time out to post your comments.

Re: Sockets and resource limit per thread

bob169728-May-08 11:45

bob16972

8-May-08 11:45

Randor wrote:
you can implement zero-byte read operations

Do you think he means put the socket in non-blocking mode, read, then put it back into blocking mode?

DWORD dwArg=1;
ioctlsocket(socketClient,FIONBIO,&dwArg); // Non-blocking mode
recv(socketClient,NULL,0,0);

dwArg=0;
ioctlsocket(socketClient,FIONBIO,&dwArg); // Blocking mode

Re: Sockets and resource limit per thread

Randor 8-May-08 12:25

Randor

8-May-08 12:25

I believe the best thing for you to do is take a look at the implementation by Len Holgate[^]. I have used his code in the past and was very impressed with the performance. It is available here:

http://www.lenholgate.com/archives/000637.html[^]

In SocketServer.cpp there is a function ZeroByteRead() which you should probably take a look at.

Best Wishes,
-David Delaune

CL.exe problem with header

Samjiman8-May-08 4:12

Samjiman

8-May-08 4:12

Hello.

I have been working on an XPCOM component project in Visual C++ 2008 Express and have been trying to create a GNU Make-compatible Makefile to build the component with CL. Compiling within the IDE works fine, but I have a strange header error when using the same command line options with CL in my Makefile. I have to address this before adding the Link step.

I have this in my Makefile:

COMPONENT = MoonshineLua
GECKOSDK = C:\gecko-sdk
SOURCES = MoonshineLua.cpp MoonshineLuaModule.cpp
PPDEFS = WIN32 _DEBUG _WINDOWS _USRDLL LUAINTERPRETER_EXPORTS _UNICODE UNICODE
LIBS = nspr4.lib xpcom.lib xpcomglue_s.lib lua.lib
FIREFOX = C:\Program Files\Mozilla Firefox 3 Beta 5
                
# create the XPCOM component
make:
        cl /Od /I "$(GECKOSDK)\include" /D "$(PPDEFS)" /Gm /EHsc /RTC1 /MDd /Fo"Debug\\" \
        /Fd"Debug\vc90.pdb" /W3 /nologo /c /ZI /TP $(SOURCES)

I get this output when I run Make:

cl /Od /I "C:\gecko-sdk\include" /D "WIN32 _DEBUG _WINDOWS _USRDLL LUAINTERPRETER_EXPORTS _UNICODE UNICODE" /Gm /EHsc /RTC1 /MDd /Fo"Debug\\" \
	/Fd"Debug\vc90.pdb" /W3 /nologo /c /ZI /TP MoonshineLua.cpp MoonshineLuaModule.cpp
MoonshineLuaModule.cpp
c:\gecko-sdk\include\prtypes.h(61) : fatal error C1083: Cannot open include file: 'stddef.h': No such file or directory
MoonshineLua.cpp
c:\gecko-sdk\include\prtypes.h(61) : fatal error C1083: Cannot open include file: 'stddef.h': No such file or directory
Generating Code...
make: *** [make] Error 2

I checked prtypes.h and sure enough it includes stddef.h. This is a standard C header, so what is the problem? I know it must not be a problem, since I can build the component within the IDE wrong. So how can I solve this for use in the Makefile or the command line in general?

Thanks for any help. Smile | :)

Re: CL.exe problem with header

CPallini8-May-08 4:25

CPallini

8-May-08 4:25

Probably you have to add an option similar to

/I "C:\gecko-sdk\include"

for the folder containing stddef.h.
Smile | :)

If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

Re: CL.exe problem with header [modified]

Rajkumar R8-May-08 4:30

Rajkumar R

8-May-08 4:30

"make" cannot find the path for stddef.h, standard VS includes

You may go for trying make file project,
Or try setting the environment variables for Visual Studio Tools,
I don't know its path, in vs2005 it is vsvar32.bat, execute it before make in the command line

see this, [Building a C/C++ Program on the Command Line^]

modified on Thursday, May 8, 2008 10:39 AM

Re: CL.exe problem with header [modified]

Samjiman8-May-08 4:56

Samjiman

8-May-08 4:56

Thanks, guys.

Running vsvar32.bat before CL does seem to be the easiest way:
http://msdn.microsoft.com/en-us/library/f2ccy3wt.aspx[^]

I will try it.

modified on Thursday, May 8, 2008 11:02 AM

Re: CL.exe problem with header

Samjiman8-May-08 12:17

Samjiman

8-May-08 12:17

Thanks for your help.

I got it working with this:

# build the XPCOM component
make:
        cl /Od /c /I "$(GECKOSDK)\include" /I "$(MSVC)\include" /D "$(PPDEFS)"  \
        /Gm /ZI /EHsc /MDd /Fo"Debug\\" /W3 /nologo /TP $(SOURCES)
        
        link /OUT:"Debug\$(COMPONENT).dll" /NOLOGO \
        /LIBPATH:"$(GECKOSDK)\lib" /LIBPATH:"$(MSVC)\lib" /LIBPATH:"$(WINSDK)\Lib" \
        /DLL /MANIFEST /DEBUG /SUBSYSTEM:WINDOWS /MACHINE:X86 \
        Debug\$(COMPONENT).obj Debug\$(COMPONENT)Module.obj $(LIBS)

capturing close button

Anandi.VC8-May-08 3:09

Anandi.VC

8-May-08 3:09

in a dialog box ,there will be minimize,maximize,close buttons at the right-top end of the window.

if i click on close button , how to capture it ?

thanks in advance,
Anandi VC

Re: capturing close button

Iain Clarke, Warrior Programmer8-May-08 3:15

Iain Clarke, Warrior Programmer

8-May-08 3:15

WM_SYSCOMMAND / OnSysCommand / (eg)SC_CLOSE should do the trick, though I think in CDialog it ends up calling OnCancel, so you have less work to do - please verify for yourself.

Iain.

Plz sir... ^CPallini ^CPallini abuz drugz, plz plz help urgent.

Re: capturing close button

Anandi.VC8-May-08 3:17

Anandi.VC

8-May-08 3:17

Thank u

Re: capturing close button

David Crow8-May-08 4:00

David Crow

8-May-08 4:00

Anandi.VC wrote:
if i click on close button , how to capture it ?

The framework calls OnSysCommand(0xf060), OnClose(), and OnCancel(), in that order.

"Love people and use things, not love things and use people." - Unknown

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

Re: capturing close button

Anandi.VC8-May-08 21:24

Anandi.VC

8-May-08 21:24

Thank u David .

Anandi VC

Re: capturing close button

Anandi.VC8-May-08 21:43

Anandi.VC

8-May-08 21:43

i checked it and it is calling all the three functions you menctioned but in the following order :

1) OnClose()
2) OnCancel()
3) OnSysCommand()

Thank u ,
Anandi VC

Exception

Anandi.VC8-May-08 2:51

Anandi.VC

8-May-08 2:51

First-chance exception in DWB.exe (OLEAUT32.DLL): 0xC0000005: Access Violation.

Could any one tell me the meaning of the above sentence ?
i got this exception while working on VC6 and COM components.

thanks in advance,
Anandi VC

Re: Exception

Cedric Moonen8-May-08 2:55

Cedric Moonen

8-May-08 2:55

Anandi.VC wrote:
Could any one tell me the meaning of the above sentence ?

You did something wrong within your program. That's about all we can say about it. But I know somebody who can help you much more than us, he is called Mr. Debugger Smile | :)

Joke aside, if you want to have more information about the problem, use your debugger: step into your program around the code which causes the problem, check the call stack, verify the different variables...

Cédric Moonen
Software developer

Charting control [v1.4]

Re: Exception

Programm3r8-May-08 2:58

Programm3r

8-May-08 2:58

Cedric Moonen wrote:
he is called Mr. Debugger

lol ....

The only programmers that are better that C programmers are those who code in 1's and 0's Green Alien | [Alien]

Programm3r
My Blog: ^_^

Re: Exception

CPallini8-May-08 2:57

CPallini

8-May-08 2:57

Invalid memory access. (buggy pointer?)
Smile | :)

Re: Exception [modified]

Rajkumar R8-May-08 4:07

Rajkumar R

8-May-08 4:07

Anandi.VC wrote:
First-chance exception in DWB.exe (OLEAUT32.DLL): 0xC0000005: Access Violation.

Could any one tell me the meaning of the above sentence ?

can be invalid pointer access. and what is First-Chance exception? When Exception Occurs debugger get notified and this first pass is called "First-Chance Exception", the debugger can then decide to pass to application to run normally if the exception was not handled by the application then the debugger gets notified again and is "second-chance exception" where the application must crash.
[First and second chance exception handling^]

Several cases the first chance exceptions don’t necessarily need to be dangerous and does not mean application's code is not proper.

for instance the following code causes first chance exception message to be written in output window

try
{
	throw 100;
}
catch (...)
{
	cout << "exception";
}

try // SEH is enabled
{
	int *ptr = (int *)0x01;
	*ptr = 1000;
}
catch (...)
{
	cout << "exception";
}

but the application handled the exception, so you don't get second chance exception.
This may not be a buggy code, but if it is buggy you cannot find the exact position of exception as the default settings of the debugger won't break execution at first-chance exception, you can enable the debugger to break at First -chance Exception so that you can get the exact position. say in VS2005, "Debug->Exceptions: then check mark exception in the list". I don't remember in VS6.0 (its time to throw these old stuff dude Wink | ;)

)

modified on Thursday, May 8, 2008 11:05 AM

Re: Exception

Stephen Hewitt8-May-08 17:04

Stephen Hewitt

8-May-08 17:04

Rajkumar R wrote:
try // SEH is enabled
{
int *ptr = (int *)0x01;
*ptr = 1000;
}
catch (...)
{
cout << "exception";
}

This construct is non-standard. The C++ standard states that catch can only catch exceptions explicitly thrown via the throw keyword. Microsoft got it wrong but later added the /EH[^] switch to select the old non-standard behaviour or the behaviour mandated by the C++ standard.

Steve

Re: Exception

Rajkumar R8-May-08 18:44

Rajkumar R

8-May-08 18:44

Yes steve, you are correct that's "Microsoft specific" .
5! for the description for what i mentioned by the comment // SEH is enabled.

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.