|
From: Nicholas N. <nj...@cs...> - 2005-11-18 14:33:43
|
On Fri, 18 Nov 2005, Julian Seward wrote: >>> instruction. The problem I see is that in gdb on a Linux 2.4 machine is >>> that each PC has a PC starting with 0x800... (as expected). My tool >>> reports each PC starts with 0x3A966F... . The logrind 2 tool of C. >>> January agrees with gdb. > > Another thing is, V's address space layout isn't necessarily going to be > the same as when running natively. Use flags -d -d (twice) to see the > actual memory layout at client startup; that will tell you where the > executable/.so's really are. The code addresses for the main executable should be the same, at 0x8048000 and beyond for x86/Linux. Those in shared objects will probably be in different locations, though. The data addresses should be more or less the same for accesses to the stack and to static data from the main executable. Other data accesses may move around, though. Nick |