Page 1 of 1

VirtualBox Memory Corruption

Posted: 31. Jul 2012, 00:44
by iTzFiNaLfLaSh
I have a virtual Ubuntu 11.10 machine that I recently cloned and trnasfered the .vdi file to a different computer. However, when I was examing memory in GDB of an Apache process, for example:

x/i *0x0804bd88

GDB returns:

0x6c28c358: Cannot access memory at 0x6c28c358

and when I look at the /proc/PID/maps file of the Apache process it shows that 0x0804bd88 is part of the process' memory layout. What can I do to fix this problem?

Re: VirtualBox Memory Corruption

Posted: 31. Jul 2012, 10:00
by mpack
Minimal information needed for assistance
viewtopic.php?f=24&t=48476

Re: VirtualBox Memory Corruption

Posted: 31. Jul 2012, 13:49
by michaln
iTzFiNaLfLaSh wrote:I have a virtual Ubuntu 11.10 machine that I recently cloned and trnasfered the .vdi file to a different computer. However, when I was examing memory in GDB of an Apache process, for example:

x/i *0x0804bd88

GDB returns:

0x6c28c358: Cannot access memory at 0x6c28c358

and when I look at the /proc/PID/maps file of the Apache process it shows that 0x0804bd88 is part of the process' memory layout. What can I do to fix this problem?
Are you sure you know how to use gdb? You are trying to display (disassemble) memory at 0x6c28c358, not at 0x0804bd88, and gdb is telling you as much. If you wanted to unassemble from 0x0804bd88, you'd do 'x/i 0x0804bd88'.

This has nothing to do with virtualization.