User Tools

Site Tools


haas:fall2017:discrete:projects:bdt0

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
haas:fall2017:discrete:projects:bdt0 [2017/09/25 15:35] – [Implementation Restrictions] wedgehaas:fall2017:discrete:projects:bdt0 [2017/10/03 14:25] (current) – [Experiencing xxd] wedge
Line 100: Line 100:
       * error message should be of the form: **Error: Terminal height is less than 20 lines!**       * error message should be of the form: **Error: Terminal height is less than 20 lines!**
       * Unlike the width, the height can impact program output (taller terminals, if not otherwise throttled by a second command-line argument, can auto-expand if there is more room and data to display).       * Unlike the width, the height can impact program output (taller terminals, if not otherwise throttled by a second command-line argument, can auto-expand if there is more room and data to display).
-  * The second command-line argument is a sizing throttle (controlling the number of lines your program will display). If no argument, or a **0** is given, assume autosize (use the detected height to be your maximum in your calculations).+  * The second command-line argument is a sizing throttle (controlling the number of lines your program will display). If no argument, or a **0** is given, display the entire file.
   * Each row will display:   * Each row will display:
     * a 7-digit hex offset (referring to the first data byte on a given line)     * a 7-digit hex offset (referring to the first data byte on a given line)
Line 112: Line 112:
   * The hex values and rendered ASCII displayed will be sourced from the file specified on the command-line. While the target files for this project are less than 512 bytes, your program should be able to handle larger and smaller files, and update its display accordingly.   * The hex values and rendered ASCII displayed will be sourced from the file specified on the command-line. While the target files for this project are less than 512 bytes, your program should be able to handle larger and smaller files, and update its display accordingly.
   * If a line throttle is given, your program is to stop output of data and ASCII rendering at that line, once it completes.   * If a line throttle is given, your program is to stop output of data and ASCII rendering at that line, once it completes.
-  * Once the data in the file has been exhausted, you need to wrap up as appropriate; finish the current line (even if you have to pad spaces), display the corresponding ascii field (padding spaces as appropriate), and display the closing footer.+  * Once the data in the file has been exhausted, you need to wrap up as appropriate; finish the current line (even if you have to pad spaces), display the corresponding ascii field (padding spaces as appropriate).
   * Don't forget to **fclose()** any open file pointers! And **free()** any **malloc()**'ed or **calloc()**'ed memory.   * Don't forget to **fclose()** any open file pointers! And **free()** any **malloc()**'ed or **calloc()**'ed memory.
   * If provided (via command-line arguments), highlight the offset field and the specified address + length (see below).   * If provided (via command-line arguments), highlight the offset field and the specified address + length (see below).
Line 212: Line 212:
 It may stop to prompt you after completing each category of tests so that you can better analyze the results (or hit CTRL-c to exit out of the script and address any issues). It may stop to prompt you after completing each category of tests so that you can better analyze the results (or hit CTRL-c to exit out of the script and address any issues).
  
-For example, let's say there's a problem +For example, let's say there's a problem with the first file: 
 <cli> <cli>
 lab46:~/src/discrete/bdt0$ make check lab46:~/src/discrete/bdt0$ make check
Line 250: Line 251:
 lab46:~/src/discrete/bdt0$  lab46:~/src/discrete/bdt0$ 
 </cli> </cli>
 +
 +With the individual char and line counts, we can get some impression of things being off in more significant ways (and of course the MD5sums will not match).
 +
 +You can then run things manually to see the end results.
  
 =====Implementation Restrictions===== =====Implementation Restrictions=====
haas/fall2017/discrete/projects/bdt0.1506353743.txt.gz · Last modified: 2017/09/25 15:35 by wedge