Differences

This shows you the differences between two versions of the page.

--- notes:data:fall2022:projects:sll0 [2022/09/22 00:31] – [DEBUGGING ADVICE] mfee1
+++ notes:data:fall2022:projects:sll0 [2022/09/22 03:39] (current) – [DEBUGGING ADVICE] rcorcor1
@@ Line 49: / Line 49: @@
 **mklist()** should make a new list containing a lead and last node. These nodes point to the start and end of the list.
+Is very similar to mknode().**For Errors**: On error, return NULL.
 **getpos()** should get the position of the node passed into the function. It should look at the node passed in -> info and find that node inside the list. If that node isn't found inside the list it should return the appropriate error specified inside pos.c.
+Start a temp node at the beginning of the list and go through each node until the given node is reached, using some form of a counter to obtain that positions value.
+**For Errors**: If Null/Undefined list or node is given, return a negative one(-1). If out-out-bounds condition, return a negative two.(-2)
 **setpos()** should set a new Node* to a position specified by a number passed into the function, think of setting a tmp variable and looping to get to that position as done in sln0.
+**For Errors**: If Null/Undefined list or node is given, return a negative one(-1). If out-out-bounds condition, return a negative two.(-2)
 **insert()** should put a new node containing a value passed into the function before the specified place. This place will be passed into the function as will the new node. For optimization of your program these should utilize the setpos() and getpos() functions to set new nodes to maintain the list. The list should be able to insert before the start and anywhere else. Remember that if the node is one after the start, you will have to set the lead's right to the new node.
@@ Line 65: / Line 66: @@
 One tool that can be utilised for debugging is the gdb and make debug commands. Use the command make with the argument debug (typed as "make debug"), then run the gdb command with the executable you are debugging ("gdb ./executable"), then from the use "run {any arguments}" and it will show where your error has occured. Furthermore, with regards to debugging a specific unit test, you can make use of the tests in  sll0/unit/list/(unit test to debug). Here you will be able to compare your results with the expected results. (Unit tests are very useful!)
-An "errors" file is also made after running make default.  Checking through this may be helpful in figuring out what's going wrong if things aren't working.
+An "errors" file is also made after running make default. Checking through this may be helpful in figuring out what's going wrong if things aren't working.\\
+After running "make" your c code will be compiled, if errors are present the errors file as mentioned will prompt with a message after the compile looking like "*** There were warnings or errors during compile! Type: 'cat errors' at the prompt to view.". If you see this message, you can cat the file errors that is only available in the base sll0 directory, this file will display every error present while compiling all of the c files. You need to be careful because it shows every compile error so if many errors are present, it might be multiple files not just one, meaning there is most likely less errors than you think for the given file you are working on. \\
 =====OUTPUT SPECIFICATIONS=====
 The only program that will be displaying output is the display function, with it possessing a standard mode and an indexed mode. The standard will simply show the values one after another, such as "0 -> 3 -> 7 -> 9 -> 19 -> NULL". The indexed mode will show the list address (starting at 0) along with the index location, such that "[0] 0 -> [1] 3 -> [2] 7 ->[3] 9 -> NULL". Note that the NULL is not accompanied by a list address.

Lab46 Wiki

User Tools

Site Tools

Differences

Page Tools