Know what it was? It was compiling C++ code on a single-user system without knowing barely anything about the language, then running running that code on a multi-user system far later and finding out, hey, I'm segfaulting!
Any way I can try to patch up any possible memory leaks in my normal computer?
Name:
Anonymous2009-02-18 12:05
Memory leaks!!? AAAAAAAAAHHHHH YOU ARE NEVER GOING TO GET THAT MEMORY BACK JUST KILL YOURSELF!
>>1
Sounds like you're accessing bad/freed memory. Get out a debugger (ie, gdb+valgrind) and figure out where it's breaking, then come back with a backtrace and associated code if you really want help.
Looks like a case of stack pointer monadic overflow.
Name:
Anonymous2009-02-18 13:42
Make all virtual addresses accessible for rw. This will make segfaults impossible.
Since the kernel will likely reserve some memory in the upper half of your address space, mask every pointer with 0x7FFF... for extra security (if you don't know how to do that, cast it to an int and use abs() on it, then cast it back).