JamesFlare/CSCI-1200
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

emphasize words

Browse Source
This commit is contained in:
Jidong Xiao
2023-09-10 23:54:49 -04:00
parent c4e7fa4ba3
commit e03a31aae6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
labs/03_debugging/README.md
View File

@@ -185,9 +185,9 @@ important if your program crashes. Unfortunately, the crash often occurs inside
Therefore, when you look at the call stack the first few functions listed may not be your code. Therefore, when you look at the call stack the first few functions listed may not be your code.
This does not mean that the C++ library has an error! Instead it likely means that your code has This does not mean that the C++ library has an error! Instead it likely means that your code has
called the library incorrectly or passed the library bad data. Find the function on the stack that is the called the library incorrectly or passed the library bad data. Find the function on the stack that is the
nearest to the top of the stack that is actually your code. By typing frame N, where N is the index of nearest to the top of the stack that is actually your code. By typing *frame N*, where *N* is the index of
the function on the stack, you can examine your code and variables and you can see the line number the function on the stack, you can examine your code and variables and you can see the line number
in your code that caused the crash. Type info locals and info args to examine the data in the in your code that caused the crash. Type *info locals* and *info args* to examine the data in the
function. Type list to see the source code. function. Type list to see the source code.
7. Breakpoint on Variable Change: The last powerful debugger feature we will try today is variable 7. Breakpoint on Variable Change: The last powerful debugger feature we will try today is variable
monitoring. monitoring.