Of all addresses...
Of all addresses...
Even you non-programmers will get a kick of out this.
I compiled a an application that worked in Visual C++ 6 in a new copy of Visual Studio 2003. Unfortunately, the program didn't work; it died with an access violation. Here's the error message:
Unhandled exception at 0x77d6d9b2 in InstallStream.exe: 0xC0000005: Access violation reading location 0xbaadf00d.
I compiled a an application that worked in Visual C++ 6 in a new copy of Visual Studio 2003. Unfortunately, the program didn't work; it died with an access violation. Here's the error message:
Unhandled exception at 0x77d6d9b2 in InstallStream.exe: 0xC0000005: Access violation reading location 0xbaadf00d.
Apparently 0xbadf00d has some sort of significance on the heap after all. Figures, since I was passing a pointer to a struct on the heap to a WinAPI function. I must be doing something wrong. Pretty funny nonetheless.
Whoa! I heard the explanation for this from my data structures teacher a few years ago, but had never seen it actually happen. He had worked for Microsoft for 17 years and told us all that it's an internal practice to set uninitialized data to "BAADF00D"--making uninitialized variable errors easier to find. (Or was it dangling pointers? I can't now remember--ir's been a while.)
Gorditas literally translate as the feminine form of "little fatties". That's what they are, really; chock full o' beef (or chicken, which I prefer), lettuce, tomato, onion, cheese, and sour cream. They had actually taken them off the menu in the NY area for a while, but popular opinion forced them back.
My program is a custom installer for distributing a huge RAR file across my school's network. We need it to transfer data to play CS at LAN parties.
My program is a custom installer for distributing a huge RAR file across my school's network. We need it to transfer data to play CS at LAN parties.