"David Reid" <dreid@xxxxxxxxxxxx> wrote: >So, saw this one again... can't help but thinking this is a pointer issue :( >00000000 0016bbcf _malloc_internal+014b >fd005cb4 0016ca24 _malloc+002c >fd005cd8 00133c4a malloc+0016 It is very likely that you are overwriting the bounds of a buffer you have allocated, and since the kernel memory buffer chain is used by everything running in the kernel, any application that calls malloc or free can fault. I'm not surprised to see this. And to find a useable startadress, I would simply allocate 16MB and 128 MB memory areas, free both of them, and use the startadress that the 128 adress was given. Its unlikely that this address range gets used by the kernel again anytime soon during debugging. regards Marcus