obliterate

[Simen Kjærås]

On 13.11.2013 08:16, KlausO wrote:
> Am 13.11.2013 02:21, schrieb Andrei Alexandrescu:
>> On 11/12/13 5:10 PM, Vladimir Panteleev wrote:
>>>> * Pointers and class references: size_t.max - 65_535, i.e. 64K below
>>>> the upper memory limit. On all systems I know it can be safely assumed
>>>> that that area will cause GPF when accessed.
>>>
>>> Make that value odd. That will also guarantee a GPF on systems where
>>> unaligned pointer access is forbidden.
>>
>> Ha, I missed that. Nice!
>>
>> Andrei
>>
>
> The classics:
>
> 0xFFFFDEAD   dead
> 0xFFFFD1ED   died
>
> Not so obvious:
>
> 0xFFFFFA1D   failed
> 0xFFFFACED   (the result makes you dumb) faced
> 0xFFFFFEED   don't feed me with this
> 0xFFFFDF0F   don't follow (this pointer) or (you are) f*****

I thought I recalled some system initializing its data to 0xF001, but 
apparently it was Algol 68-R using the character string 
"FOOLFOOLFOOL..."[0].

Still, I guess a case could be made for 0xFFFFF001.

[0]: http://www.catb.org/jargon/html/F/fool.html

--
   Simen