You have to run msvcmon.exe on the remote machine before trying to connect to it from the debugger. Check msvcmon.exe in the MSDN (To use the tcpip without a password and without timeout, issue the command: msvcmon.exe -tcpip -anyuser -timeout -1) Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Your problem is that you have a lot of NON matching braces for example: { <-------------------------------- here display_statement (a, b, c, d, x, e); return 0; void display_statement (double payment, double loan_payment, double Tinterest, double Principal, int Number_Payments, double interestrate) { <-------------------------------- here printf("Monthy Payment: $%.2f\n\n", payment); printf("Total Loan Amount; $%.2f\n\n", loan_Amount); printf("Total Interest Payment: $%.2f\n\n", Tinterest); printf("Principal: $%.2f\n\n", Principal); printf("Number Of Payments: %d\n\n", Number_Payments); printf("Interest Rate %.3f percent\n\n", interestrate); } <-------------------------------- here Papa while (TRUE) Papa.WillLove ( Bebe ) ;

.hpp / .h++ / .hxx / .hh for C++ headers. .h should be reserved for C headers This is not respected though Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Check the prebuild steps in the project settings Papa while (TRUE) Papa.WillLove ( Bebe ) ;

The address 0xabababab indicates a memory following a block allocated by LocalAlloc(). Means that you are stepping (wayyy) outside of your memory block Try setting a conditional break point on when the variable study change Papa while (TRUE) Papa.WillLove ( Bebe ) ;

You can find the code in dbgheap.c under \crt\src see what can be done It mainly uses IsBadReadPtr, IsBadWritePtr and HeapValidate or __sbh_verify_block depending on the OS and if the CRT is statically or dynamically linked Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Can you show how and where are you doing the declaration? Papa while (TRUE) Papa.WillLove ( Bebe ) ;

This means that you defined "variable" in more than a file, and both defines it as public If each one should have its copy, try putting static in front of them If the variable should be shared, declare it as extern in one of the files Papa while (TRUE) Papa.WillLove ( Bebe ) ;

I know that they are currently working on new features in Purify plus Papa while (TRUE) Papa.WillLove ( Bebe ) ;

What about using the pragma warning?? Papa while (TRUE) Papa.WillLove ( Bebe ) ;

http://www.unknownroad.com/rtfm/VisualStudio/warningC4251.html[^] Papa while (TRUE) Papa.WillLove ( Bebe ) ;

At work we use purify, and it works quite good and is a pretty fast solution for finding memory related problems. I tried boundschecker and its also pretty good, it integrate several error checking capabilities like the thing you mentioned, and more (deadlock detection, call validation, object tracking, .NET analysis ...) Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Seeing the older posts he made, i guess he is trying to code a worm but using VB :) Papa while (TRUE) Papa.WillLove ( Bebe ) ;

I know that these macros often resolve to param = param; which is a junk code just to reference the param. The commenting of the param just instruct the compiler to *not see* the param in order to skip the warning Papa while (TRUE) Papa.WillLove ( Bebe ) ;

The bug slayer, John Robbins, in his Debugging Applications for Microsoft .NET and Microsoft Windows (Great book btw) Papa while (TRUE) Papa.WillLove ( Bebe ) ;

This is the best way thought void Function(int param1, int /*param2*/) { } Papa while (TRUE) Papa.WillLove ( Bebe ) ;

http://www.codeproject.com/cs/miscctrl/listboxex.asp[^] In this article you also have some links: http://www.codeproject.com/wtl/WTL_EditListBox.asp[^] Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Exactly. But the same hash is also needed in the first case when using API hooking. Should be noted that both techniques lacks info on the files that where opened before the startup of our code, so basically its better to start before any user process. So its add some tiny complication to our friends request. Good luck anyway! Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Maybe he meant to use some API Hooking on the CreateFileXXX family of functions in order to monitor what files are open. But i guess this method isn't so good. Writing a driver may offer a better solution, with a file system filter IFSMGR_InstallFileSystemApiHook in order to be in the chain of all file system requests. (Windows 9x) or a file system driver that attach a filter device objects to target file system device objects so that it see all IRPs and FastIO requested from drives. A hash is necessary to keep track of the correspondance of HANDLE <-> Pathname Papa while (TRUE) Papa.WillLove ( Bebe ) ;

Didn't try it on a IE addon. But why dont you try to hard code a breakpoint in your code, that will launch the debugger automatically? add this line to the function of your choice in your add in __asm int 3 Papa while (TRUE) Papa.WillLove ( Bebe ) ;