190
edits
Changes
m
please feel free to change the contents' depth!!!
In order to add a new process you need to find the .pdb files.
The debugger needs access to these files of the '''Multiple processes'''
'''Multiple [[File:Process-addprocess.png|1000px|center|Process window]] You could also attach a process outside of the debugger to the debugger, including processes'''on a remote device but your inspection ability is limited.*1. Choose the Debug menu ant click Attach to Process*2. Select the process you want to attach [[File:Process-addprocess.png|1000px|center|Process window]] You could also set process to automatically start in the debugger which is useful for services and custom setup actions.*1. Start regedit*2. Got to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Image File Execution Options*3. Select the folder of the application you want to start in debugger*4. In the folder right click and choose New, String Value.*5. Set name of new value from New Value to debugger.*6. Right clikc the new value and choose Modify.*7. On the Edit String dialog box, type vsjitdebugger.exe in the Value data box.
Each project is an individual process[[File:Process-startupprocess.png|center|Process window]]
If you have more than one project in a project solution, you can choose which projects the debugger starts
You could also attach a process outside of the debugger to the debugger, including processes on a remote device but your inspection ability is limited
You could also set When you have multiple processes, only one process to automatically start is active in the debugger – useful for services and custom setup actions, but in order to switch between processes you must also be in break mode.[[File:Process-switchprocess.png|1000px|center|Process window]]
When you have multiple processes, only one process is active in the debugger, but in order to switch between processes, you must be in break mode
When the thread is multiple.[[File:tt_2.png|400px|center|2]] [[File:tt2_d.png|400px|center|2]]
→Group Members
# [mailto:ashimazaki@myseneca.ca?subject=GPU621 Azusa Shimazaki]
# [mailto:oasturiano@myseneca.ca?subject=GPU621 Orlandson Asturiano]
=Process and thread=
*2. Go to general page and toggle "Break all processes when one process breaks" checkbox
[[File:ExampleProcess-config.jpgpng|1000px|center|Process window]]
If you have more than one project in a project solution, you can choose which projects the debugger starts.pdb file holds the debugging and project state info that’s created on compile
To do this:
*1. Right click your solution in solution explorer
*2. Select Set Startup Projects
*3. Then set the projects action to Start, Start without debugging or none
When you switch to a process, all windows will show information for that process only.
When you stop debugging, if the current process was launched from the debugger it will terminate, however if you attached the debugger to the current process (attach to a process outside of vs2017Visual Studios), then the debugger will detach and leave that process running.
==Thread==
*Process Name: the process to which each thread belongs.
==Source window== The Source window displays source code [[File:source_window2.png|1000px|center|Source window]] '''Setup:''' 1. When you start debug (F5), it shows up automatically 2. If you closed the window, you can open by clicking any related information on the other windows. '''How to Use:''' On the top of the window, Turn on an icon called "Show Threads in Source" that is off by default.[[File:op_off.png|50px|center|off]] [[File:op_on.png|50px|center|on]]Or you can do on and off from right-click menu on the thread window.[[File:show_op.png|300px|center|show]] On the gutter, you can see thread icon where the threads are currently working.Also, you can check the detail of the threads with mouse over. When the thread is single (at the beginning of the threading):[[File:tt_1.png|400px|center|1]] [[File:tt1_d.png|200px|center|1]]
==Debug Location toolbar==