138: Pointers
Divad27182 (Talk | contribs) (→Explanation: on the pointers themselves...) |
|||
| Line 10: | Line 10: | ||
The "segmentation fault" the image text is referencing also arises from this kind of memory access. If you define a pointer to an invalid address, then try to access the memory location associated with it, you could end up with this exception. The hexadecimal address 0x-1 is one of those invalid access pointers, because memory locations generally start at numeric location 0. | The "segmentation fault" the image text is referencing also arises from this kind of memory access. If you define a pointer to an invalid address, then try to access the memory location associated with it, you could end up with this exception. The hexadecimal address 0x-1 is one of those invalid access pointers, because memory locations generally start at numeric location 0. | ||
| + | |||
| + | The "pointers" given are interesting in that all the bytes are printable ASCII characters. | ||
| + | In this case (and assuming network byte order), "''':(!:'''", "'''c99,'''", and "'''sch.'''". | ||
| + | It is also interesting that the values that are followed by punctuation each end in that punctuation. | ||
{{Comic discussion}} | {{Comic discussion}} | ||
Revision as of 23:14, 13 October 2012
Image Text
Every computer, at the unreachable memory address 0x-1, stores a secret. I found it, and it is that all humans ar—SEGMENTATION FAULT.
Explanation
This comic is about a play on the dual meaning of the word “pointer”. Cueball is playing a computer game in the comic, but he seems to be stuck. So he askes Black Hat for a few tips (“pointers”) to get unstuck again. Black Hat wants to be annoying, so he spits out a couple of (seemingly random) 32-bit hexadecimal addresses, which are “pointers” in a programming language. These pointers are used to access a certain location in the computer's memory in order to fulfill a task. Cueball then hates Black Hat for not answering his question.
The "segmentation fault" the image text is referencing also arises from this kind of memory access. If you define a pointer to an invalid address, then try to access the memory location associated with it, you could end up with this exception. The hexadecimal address 0x-1 is one of those invalid access pointers, because memory locations generally start at numeric location 0.
The "pointers" given are interesting in that all the bytes are printable ASCII characters. In this case (and assuming network byte order), ":(!:", "c99,", and "sch.". It is also interesting that the values that are followed by punctuation each end in that punctuation.
add a comment!Discussion
- --done (yes, anyone can fix this.) Divad27182 (talk) 18:49, 23 February 2013 (UTC)
