My socket application fails when run under BoundsChecker

0 Likes

Problem:

I have an Asychronous Socket application.  When running using the integrated debugging or when running under BoundsChecker Standalone, Connect always returns 0.  It works fine when not using BC.

Resolution:

The Asych Socket uses GetLastError for connect.  BoundsChecker resets this by default, causing Connect() to fail.  The solution is to uncheck that in the settings dialog.  Open your exectuable in BoundsChecker, go to the settings dialog box, select custom error detection mode.  The category "Reset GetLastError.." is under is "API and OLE Error Detection".  Make certain this box is not selected.

Old KB# 12186
Comment List
Anonymous
Related Discussions
Recommended