{"id":7266,"date":"2025-12-06T00:01:59","date_gmt":"2025-12-06T08:01:59","guid":{"rendered":"https:\/\/c-for-dummies.com\/blog\/?p=7266"},"modified":"2025-12-13T08:19:37","modified_gmt":"2025-12-13T16:19:37","slug":"dumping-the-screen-in-color","status":"publish","type":"post","link":"https:\/\/c-for-dummies.com\/blog\/?p=7266","title":{"rendered":"Dumping the Screen in Color"},"content":{"rendered":"

The hexdump<\/em> utility is a marvelous tool for grabbing a sneak peek at a file’s innards, especially when debugging code that performs file access. As a text mode tool, however, it could stand to use some colorful character improvement.
\n
\nThe hexdump<\/em> utility is a filter. Run at the command prompt, it dumps a file by name or by using redirected input. Here’s a quickie test run:<\/p>\n

~$ hexdump
\nHello!
\n0000000 6548 6c6c 216f 000a
\n0000007
\n~$<\/code><\/p>\n

My favorite view is “canonical” mode, activated by using the -C<\/code> switch:<\/p>\n

~$ hexdump -C
\nHello!
\n00000000  48 65 6c 6c 6f 21 0a                              |Hello!.|
\n00000007
\n~$<\/code><\/p>\n

Seeing both the hex dump and ASCII equivalents can truly help disclose a file’s contents. In fact, I used hextdump<\/em> a few days ago to dump some word processing files saved years ago by antique software. This tool helped me view the text portion of correspondence, which saves time tussling with Microsoft Word to extract text.<\/p>\n

The Exercise for March 2020<\/a> was to code a hexdump<\/em>-like utility. My solution involved reading a file for input, though it can easily be converted into a filter for more flexible input. I’ll use this program as a base for my updated hexdump<\/em>\/color utility, though it requires lotsa modification.<\/p>\n

My first goal is to decide how to use colors to help present more than just a period in the ASCII column for non-printable characters. For example, control codes can be output color-coded red. Each code has a corresponding character: ^@ for the null character (\\0), ^A for control code 1, ^B for 2, on up to ^_ for code 31. No standard equivalent exists for code 127, the “delete” character: Unicode U-2421 (␡) is often used on the web as well as U-247F ( ⑿ for some reason).<\/p>\n

The following code churns through ASCII values zero through 127. For the control codes (values zero through 31), the corresponding character is output in red:<\/p>\n

2025_12_06-Lesson.c<\/a><\/h3>\n
\r\n#include <stdio.h>\r\n\r\n#define RED \"\\e[31m\"\r\n#define NORMAL \"\\e[m\"\r\n\r\nint main()\r\n{\r\n    unsigned char ch;\r\n\r\n    for( ch=0; ch<=127; ch++ )\r\n    {\r\n        printf(\"%02X %03d \",ch,ch);\r\n        if( ch<32 )\r\n            printf(\"%s%c%s\",RED,ch+'@',NORMAL);\r\n        else\r\n            putchar(ch);\r\n        putchar('\\n');\r\n    }\r\n    return 0;\r\n}<\/pre>\n
Variable ch<\/code> is declared as an unsigned char<\/em>, which prevents the for<\/em> loop from repeating endlessly. (A signed value resets ch<\/em> negative after 127 and the loop continues endlessly.)<\/p>\n
Within the for<\/em> loop, the hexadecimal and decimal values of variable ch<\/code> are output. When ch<\/code> is less than 32, its ASCII equivalent character is output color-coded red. Otherwise, the character is output directly. Refer to this blog post<\/a> for information on ANSI color text output.<\/p>\n
Here’s a truncated sample run:<\/p>\n
00 000 @<\/span>
\n01 001 A<\/span>
\n02 002 B<\/span>
\n03 003 C<\/span>
\n04 004 D<\/span>
\n05 005 E<\/span>
\n06 006 F<\/span>
\n07 007 G<\/span>
\n...
\n78 120 x
\n79 121 y
\n7A 122 z
\n7B 123 {
\n7C 124 |
\n7D 125 }
\n7E 126 ~
\n7F 127<\/code><\/p>\n
For value 127 (del), I’d like to output the Unicode character ␡ as the equivalent. Additionally, for character code values 128 through 255, special characters can also be generated, perhaps in color. In fact, equivalents for the control code characters exist as well: code 0, ^@ is ␀. This update to the code requires that I retrofit it with wide character output. I begin this task in next week’s Lesson<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
One of my favorite command line tools can do with some colorful improvement. Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-7266","post","type-post","status-publish","format-standard","hentry","category-main"],"_links":{"self":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7266","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=7266"}],"version-history":[{"count":13,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7266\/revisions"}],"predecessor-version":[{"id":7310,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/7266\/revisions\/7310"}],"wp:attachment":[{"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=7266"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=7266"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/c-for-dummies.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=7266"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}