Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » data » fall2022 » projects » sll4
notes:data:fall2022:projects:sll4

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
notes:data:fall2022:projects:sll4 [2022/10/18 22:31] – [PROGRAM] gsubernotes:data:fall2022:projects:sll4 [2022/10/19 23:18] (current) – [BACKGROUND] dmuck
Line 33: Line 33:
  
 Group has eight new list-group-processing functions, that are in charge of manipulating lists within our data structure. Going up one level of abstraction, lists are the new nodes! At this level, we are not worrying about manipulating nodes anymore, but only the node containers; in other words, we are only focusing on the addresses/pointers that hold lists, no more node processing this time. Group has eight new list-group-processing functions, that are in charge of manipulating lists within our data structure. Going up one level of abstraction, lists are the new nodes! At this level, we are not worrying about manipulating nodes anymore, but only the node containers; in other words, we are only focusing on the addresses/pointers that hold lists, no more node processing this time.
 +
 +Take care to check the unit-test files for other functions that are being called in the event that you have not yet implemented them.
 =====SPECIFICATIONS===== =====SPECIFICATIONS=====
  
Line 58: Line 60:
 //ldisplay()//'s behavior indicates that //"on an error state, output "<ERROR>", return -2"//, the error state in this case would be an invalid position. //ldisplay()//'s behavior indicates that //"on an error state, output "<ERROR>", return -2"//, the error state in this case would be an invalid position.
 =====UNIT TESTS===== =====UNIT TESTS=====
-Unit tests will rely upon one another as input/output/modifications to the list. A good majority of the functions call on display, so if you haven't completed display while checking it might lead to some issues. Make sure if you are getting issues that it isn't the unit test calling upon a not yet implemented function. Your display function will print **NOT YET IMPLEMENTED** if it isn't finished yet.+Unit tests will rely upon one another as input/output/modifications to the list. A good majority of the functions call on display, so if you haven't completed display while checking it might lead to some issues. Make sure if you are getting issues that it isn't the unit test calling upon a not yet implemented function. Your display function will print **NOT YET IMPLEMENTED** if it isn't finished yet. Also, for some functions such as append, you might want to first do getpos/setpos, that way it will be easier to implement. 
 + 
 +An errors file will be created after running make, this may be helpful if things aren't compiling correctly.
 =====DEBUGGING===== =====DEBUGGING=====
 Useful tools for debugging issues are gdb and examining the test files themselves. to utilize gdb, run the test program with the gdb command (not make check), with a command that might look like "gdb ./bin/unit-lobtain". Once in gdb the "run" command with start the program, and "break (line number)" will cause the program to stop at the specified line number. Once you have hit the breakpoint you can use "display (variable name)" to see the value of a variable at every step, "n" to step to the next line, and "continue" to continue running the program until the next breakpoint. Note that if you encounter a seg fault the program will tell the where the seg fault occurs, and you can use "run" again to restart the program. Useful tools for debugging issues are gdb and examining the test files themselves. to utilize gdb, run the test program with the gdb command (not make check), with a command that might look like "gdb ./bin/unit-lobtain". Once in gdb the "run" command with start the program, and "break (line number)" will cause the program to stop at the specified line number. Once you have hit the breakpoint you can use "display (variable name)" to see the value of a variable at every step, "n" to step to the next line, and "continue" to continue running the program until the next breakpoint. Note that if you encounter a seg fault the program will tell the where the seg fault occurs, and you can use "run" again to restart the program.
notes/data/fall2022/projects/sll4.1666132264.txt.gz · Last modified: 2022/10/18 22:31 by gsuber

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki