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

emphasize gdb commands

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

2
labs/03_debugging/README.md
View File

@@ -188,7 +188,7 @@ called the library incorrectly or passed the library bad data. Find the function
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.
Add a new modifier member function to the *Point* class named *set_elevation* that changes the *y* coordinate of a *Point* instance. Create an instance of a *Point* object in the *main* function called *pt*. Add a new modifier member function to the *Point* class named *set_elevation* that changes the *y* coordinate of a *Point* instance. Create an instance of a *Point* object in the *main* function called *pt*.