![[challenge entry]](/images/board_posticon_c.gif "Challenge Entry: Computer Errors"){kind=small}
From the Computer Errors challenge. See all 396 entries (closed)
(
Puromycin is still licking windows,
Sun 24 Jun 2007, 23:46,
archived)
arf!someone who occasionally calls me for advice when stuff crashes insists on reading out all those sodding numbers assuming they'll mean something to me
(
eclectech is older but no wiser,
Sun 24 Jun 2007, 23:49,
archived)
Memory dumpSitting on the toilet trying to remember what the fuck those numbers mean.
/20+years of programming blog
(/20+years of programming blog
Puromycin is still licking windows,
Sun 24 Jun 2007, 23:54,
archived)
I always thought that itwas the most pointless debugging tool - I mean, how do you know what address the program started at?
(
Damocles wants no part of your debauchery,
Sun 24 Jun 2007, 23:58,
archived)
I usually askthe program's parents
( Puromycin is still licking windows,
Mon 25 Jun 2007, 0:02,
archived)
my program killed it'sparents when it set fire to the family home.
( Damocles wants no part of your debauchery,
Mon 25 Jun 2007, 0:05,
archived)
Serious answer?It's actually very useful. Programs usually load at the same address, and you can then use either the map file or load the program into memory with a debugger (on the same OS version) to find out where the address is.
In that case the error can be narrowed down considerably, although a process dump is much more useful than just an address.
The problem is moot, though; various Unixes/Vista support Address Space Layout Randomization (ASLR) to make stack overflow/code injection attacks etc harder. This changes the base load address of the process, and thus probably renders the memory address of a crash useless.
(,
Tue 26 Jun 2007, 11:50,
archived)
In that case the error can be narrowed down considerably, although a process dump is much more useful than just an address.
The problem is moot, though; various Unixes/Vista support Address Space Layout Randomization (ASLR) to make stack overflow/code injection attacks etc harder. This changes the base load address of the process, and thus probably renders the memory address of a crash useless.