Lab46 Wiki

User Tools

Site Tools

You are here: start » haas » spring2016 » cprog » projects » cbf0
haas:spring2016:cprog:projects:cbf0

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:spring2016:cprog:projects:cbf0 [2016/03/21 22:58] – [20 line Throttled display (on a file of 512 bytes)] wedgehaas:spring2016:cprog:projects:cbf0 [2016/03/22 19:56] (current) – [Unthrottled display (512 bytes)] wedge
Line 57: Line 57:
       * 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).
-  * If a second command-line argument exists, assume it is a sizing throttle (controlling the number of lines your program will display). If no argument is given (or that argument is a **0**), 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 a  **0** is given, assume autosize (use the detected height to be your maximum in your calculations).
   * Display an ASCII header identifying the various fields (offset, hex, ascii), surrounded by dashed lines, running 79 characters in width. See below for more details.   * Display an ASCII header identifying the various fields (offset, hex, ascii), surrounded by dashed lines, running 79 characters in width. See below for more details.
   * Each row after the header will display:   * Each row after the header will display:
Line 110: Line 110:
  
 <cli> <cli>
-lab46:~/src/cprog$ ./hexview win7.mbr+lab46:~/src/cprog$ ./hexview win7.mbr 0
 ------------------------------------------------------------------------------- -------------------------------------------------------------------------------
 offset      0  1  2  3   4  5  6  7   8  9  a  b   c  d  e  f  ascii offset      0  1  2  3   4  5  6  7   8  9  a  b   c  d  e  f  ascii
Line 178: Line 178:
 lab46:~/src/cprog$  lab46:~/src/cprog$ 
 </cli> </cli>
 +
 +====30 line throttled display (on a 217 byte file)====
 +
 +This example demonstrates the scenario where there isn't enough data to complete not only the specified number of lines, but not even the line it was displaying. In such a case, we pad the line with spaces out to the end (both data and ascii fields) so that everything lines up (note the display of the ascii for whatever data was present on the line).
 +
 +<cli>
 +lab46:~/src/cprog$ ./hexview shortfall.mbr 30
 +-------------------------------------------------------------------------------
 +offset      0  1  2  3   4  5  6  7   8  9  a  b   c  d  e  f  ascii
 +-------------------------------------------------------------------------------
 +0x00000000 eb 63 90 10  8e d0 bc 00  b0 b8 00 00  8e d8 8e c0  .c..............
 +0x00000010 fb be 00 7c  bf 00 06 b9  00 02 f3 a4  ea 21 06 00  ...|.........!..
 +0x00000020 00 be be 07  38 04 75 0b  83 c6 10 81  fe fe 07 75  ....8.u........u
 +0x00000030 f3 eb 16 b4  02 b0 01 bb  00 7c b2 80  8a 74 01 8b  .........|...t..
 +0x00000040 4c 02 cd 13  ea 00 7c 00  00 eb fe 00  00 00 00 00  L.....|.........
 +0x00000050 00 00 00 00  00 00 00 00  00 00 00 80  01 00 00 00  ................
 +0x00000060 00 00 00 00  ff fa eb 07  f6 c2 80 75  02 b2 80 ea  ...........u....
 +0x00000070 74 7c 00 00  31 c0 8e d8  8e d0 bc 00  20 fb a0 64  t|..1....... ..d
 +0x00000080 7c 3c ff 74  02 88 c2 52  be 80 7d e8  1c 01 be 05  |<.t...R..}.....
 +0x00000090 7c f6 c2 80  74 48 b4 41  bb aa 55 cd  13 5a 52 72  |...tH.A..U..ZRr
 +0x000000a0 3d 81 fb 55  aa 75 37 83  e1 01 74 32  31 c0 89 44  =..U.u7...t21..D
 +0x000000b0 04 40 88 44  ff 89 44 02  c7 04 10 00  66 8b 1e 5c  .@.D..D.....f..\
 +0x000000c0 7c 66 89 5c  08 66 8b 1e  60 7c 66 89  5c 0c c7 44  |f.\.f..`|f.\..D
 +0x000000d0 06 00 70 b4  42 cd 13 72  05                        ..p.B..r.       
 +-------------------------------------------------------------------------------
 +lab46:~/src/cprog$ 
 +</cli>
 +
 +=====Bonus Opportunities=====
 +The following can be considered a bonus point opportunity:
 +
 +  * Enhance the program to accept up to 6 pairs of additional values (offset followed by its length), where each offset through length will be colored using ANSI text escape sequences.
 +  * For any line containing this colorized text, highlight the address in bold white.
 +
 +====Sample output====
 +
 +As an example, running the program with the following arguments could produce results like this:
 +
 +<cli>
 +lab46:~/src/cprog$ ./hexview win7.mbr 0 0x1be 1 0x1c2 1 0x1c6 4 0x1ca 4 0x1fe 2
 +</cli>
 +
 +{{:haas:spring2016:cprog:projects:hexviewer.png?640|}}
 +====ANSI escape sequences for color====
 +This probably isn't very portable, and depending on the terminal, it may not work for some people.
 +
 +It may be most convenient to set up preprocessor #define statements near the top of your code, as follows:
 +
 +<code c>
 +#define  ANSI_RESET             "\x1b[0m"
 +#define  ANSI_BOLD              "\x1b[1m"
 +#define  ANSI_FG_BLACK          "\x1b[30m"
 +#define  ANSI_FG_RED            "\x1b[31m"
 +#define  ANSI_FG_GREEN          "\x1b[32m"
 +#define  ANSI_FG_YELLOW         "\x1b[33m"
 +#define  ANSI_FG_BLUE           "\x1b[34m"
 +#define  ANSI_FG_MAGENTA        "\x1b[35m"
 +#define  ANSI_FG_CYAN           "\x1b[36m"
 +#define  ANSI_FG_WHITE          "\x1b[37m"
 +#define  ANSI_BG_BLACK          "\x1b[40m"
 +#define  ANSI_BG_RED            "\x1b[41m"
 +#define  ANSI_BG_GREEN          "\x1b[42m"
 +#define  ANSI_BG_YELLOW         "\x1b[43m"
 +#define  ANSI_BG_BLUE           "\x1b[44m"
 +#define  ANSI_BG_MAGENTA        "\x1b[45m"
 +#define  ANSI_BG_CYAN           "\x1b[46m"
 +#define  ANSI_BG_WHITE          "\x1b[47m"
 +</code>
 +
 +To use, you output them:
 +
 +<code>
 +fprintf(stdout, ANSI_FG_GREEN);
 +fprintf(stdout, "This text is green\n");
 +fprintf(stdout, ANSI_RESET);
 +</code>
 +
 +You have to remember to turn the color or setting off (resetting it) to revert back to the original color.
 +
 +You can mix and match as well:
 +
 +<code>
 +fprintf(stdout, ANSI_FG_YELLOW);
 +fprintf(stdout, ANSI_BG_BLUE);
 +fprintf(stdout, ANSI_BOLD);
 +fprintf(stdout, "This text is bold yellow on blue\n");
 +fprintf(stdout, ANSI_RESET);
 +</code>
 +
 +While there are 8 available foreground colors, bolding can double that range to 16.
 =====Submission===== =====Submission=====
 To successfully complete this project, the following criteria must be met: To successfully complete this project, the following criteria must be met:
  
   * Code must compile cleanly (no warnings or errors)   * Code must compile cleanly (no warnings or errors)
-  * Final image must be viewable.+    * Use the **-Wall** flag when compiling.
   * Code must be nicely and consistently indented (you may use the **indent** tool)   * Code must be nicely and consistently indented (you may use the **indent** tool)
-  * Code must utilize the specifications presented above+  * Code must utilize the algorithm/approach presented above 
 +  * Output **must** match the specifications presented above (when given the same inputs)
   * Code must be commented   * Code must be commented
     * have a properly filled-out comment banner at the top     * have a properly filled-out comment banner at the top
Line 190: Line 281:
   * Track/version the source code in a repository   * Track/version the source code in a repository
   * Submit a copy of your source code to me using the **submit** tool.   * Submit a copy of your source code to me using the **submit** tool.
-    * You are to submit 3 files: 
-      * your C source code to accomplish this task 
-      * your copy of out.file 
-      * your processed cbf0.jpg file 
  
 To submit this program to me using the **submit** tool, run the following command at your lab46 prompt: To submit this program to me using the **submit** tool, run the following command at your lab46 prompt:
  
 <cli> <cli>
-$ submit cprog cbf0 cbf0.c cbf0.file /home/username/public_html/cbf0.jpg+$ submit cprog cbf0 cbf0.c
 Submitting cprog project "cbf0": Submitting cprog project "cbf0":
     -> cbf0.c(OK)     -> cbf0.c(OK)
-    -> cbf0.file(OK) 
-    -> /home/username/public_html/cbf0.jpg(OK) 
  
 SUCCESSFULLY SUBMITTED SUCCESSFULLY SUBMITTED
haas/spring2016/cprog/projects/cbf0.1458601123.txt.gz · Last modified: 2016/03/21 22:58 by wedge

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