This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: examining a core dump on a machine with other base addresses in shared libraries

On Wed, May 27, 2009 at 1:52 PM, Drago Krznaric <> wrote:

> I have a program and a core dump created on machine A that I copy to
> machine B. I can open the core dump and get a nice backtrace on A but
> not on B. The reason appears to be that the shared libraries on A and B
> have different base addresses. They are otherwise exactly identical in
> hardware and software (RedHat 4).

Are you absolutely sure the libc binaries are identical between A and B?
We see a lot of similar GDB failures due to mismatch between libc versions
(but we don't use prelink).

You could verify whether prelink is the problem, by copying and to e.g. /tmp/lib, manually prelinking them to the same
address and were prelinked at, and verifying
they "work" (set solib-absolute-prefix /tmp in GDB before loading the core).

I think you should also get identical (as in md5sum-identical) binary
for B:/tmp/lib/ and A:/lib/

Paul Pluzhnikov

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]