Controversial Book Cover?

Some people commented that by placing an image of a complete memory dump on the back cover of a book both violates copyright and intellectual property rights, as the picture is generated from copyrighted material. Instead they suggested to put a picture of a freeware program. Here is my response:

I disagree to the best of my understanding. This picture is just the visualized physical memory for illustration purposes only. What about disassembling a function to illustrate a bug? Or dumping memory, for example, a thread structure? Or printing a screenshot from Performance Monitor or Task Manager to illustrate CPU spike? Or a stack trace from a complete memory dump? Does it violate copyright and intellectual property rights because it is generated from copyrighted material? What about the front cover then, showing book spines of hundreds of copyrighted books? If Microsoft asks me to remove the picture, certainly, I’ll do it and reprint the book. And, surely, a memory dump of a freeware program will definitely contain portions of copyrighted material, like ntdll.dll, kernel32.dll or accidental 3rd-party hooks. Regarding a complete memory dump copyrighted material might have been paged out from physical memory and not included in file contents. Do you admit that printing a CRC number violates property rights because it was generated from copyrighted material? Due to the mathematical nature of involved algorithms it is not possible to reconstruct binary code from the printed cover picture which could have been created artificially as well.

What do you think?

- Dmitry Vostokov @ -

4 Responses to “Controversial Book Cover?”

  1. Dmitry Vostokov Says:

    Using my CRC example, there are many ways (different code and data) to get the same picture because it was first preprocessed and reduced from 16128×16128 to 2167×3254 format and further processed by JPEG algorithm. I would say that we have a different interpretation of the data if the original data is not possible to reconstruct or if there is ambiguity in data reconstruction. Also we will never get the same picture from different memory dumps even from the same system because memory contents and layout change with every CPU tick. How would I get exactly the same picture form a different code and data? Exactly the same way I can generate the same CRC!

  2. Dmitry Vostokov Says:

    I actually found that a user dump of one of my applications is much better and vivid picture to illustrate. So I’ll replace the picture in the final book. To sleep better :-)

  3. Mario Hewardt Says:

    This link may be useful:

    At least in as far as screenshots of Microsoft products is concerned.

  4. Crash Dump Analysis » Blog Archive » Final Back Cover for MDAA V1 Says:

    […] Crash Dump Analysis Exploring Crash Dumps and Debugging Techniques on Windows Platforms « Controversial Book Cover? […]

Leave a Reply

You must be logged in to post a comment.