How to debug code between different project?

The above is a DLL project, here is a test project, which is used to call DLL function
In 16 rows added a breakpoint, debugging when how to enter cltSocketInit function?
Ps: function definitions are not written in the following test project, only in the project below statement is written in the header file
Attach a debug interface:

Ps: debugging in Visual Studio 2010 can enter the function definition, but can not in 2015, is there any way

CodePudding user response:

DLL project choice "attach to process", it is still the same, of course, the most convenient solution, additional kind of trouble every time,
Exe program, of course, to load generated DLL folder, copy the invalid (apparently, they are not tested)

CodePudding user response:

reference 1st floor dustpg response:

DLL project choice "attach to process", it is still the same, of course, the most convenient solution, additional kind of trouble every time,
Exe program, of course, to load generated DLL folder, copy the invalid (apparently, they are not tested)

Is in the same solution, only belong to a solution under different project, VS2010 can open two solutions respectively, and then step through, but VS2015 can not

CodePudding user response:

refer to the second floor u010320019 response:

Quote: refer to 1st floor dustpg response:

DLL project choice "attach to process", it is still the same, of course, the most convenient solution, additional kind of trouble every time,
Exe program, of course, to load generated DLL folder, copy the invalid (apparently, they are not tested)

Is in the same solution, only belong to a solution under different project, VS2010 can open two solutions respectively, and then step through, but shouldn't VS2015

My vs2015 no problem ╮ (￣ del ￣) ╭

CodePudding user response:

The building Lord, I encountered a similar problem, after the DLL in the same solution can't see the value of a variable, could you tell me how to solve this problem, you are looking forward to reply

CodePudding user response:

CodePudding user response:

reference 1st floor dustpg response:

DLL project choice "attach to process", it is still the same, of course, the most convenient solution, additional kind of trouble every time,
Exe program, of course, to load generated DLL folder, copy the invalid (apparently, they are not tested)

This is can



The command set for your exe application can in the DLL breakpoint debugging