Re: [RFC/ia64] memory error when reading wrong core file

[Jan Kratochvil <jan.kratochvil@redhat.com>]

Hi Joel,

On Fri, 29 Jan 2010 17:02:22 +0100, Joel Brobecker wrote:
> Contrast this with what we get today, on ia64-linux:
> 
>     (gdb) core core
>     warning: core file may not match specified executable file.
>     [New Thread 5437]
>     Cannot access memory at address 0x1000000000009
> 
> The change of behavior is related to a patch that changed the way
> the solib base address gets computed (that was for PIE, patch 12/15
> I believe).  Prior to that patch, the computed base address was zero.

before verifying your patch I would like to check if the PIE change should not
be rather somehow fixed.  Unfortunately I am unable to reproduce the problem
on ia64 (RHEL-5.4) GDB HEAD (ea72145d5db8c66253c9b21b785a5311f69ae99e).

GNU gdb (GDB) 7.0.50.20100129-cvs
This GDB was configured as "ia64-unknown-linux-gnu".
Reading symbols from /root/.../pause...done.
[New Thread 30776]
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libc.so.6.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6.1
Reading symbols from /lib/ld-linux-ia64.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-linux-ia64.so.2
Core was generated by `./pause'.
Program terminated with signal 11, Segmentation fault.
#0  0xa000000000010620 in __kernel_syscall_via_break ()
(gdb) 

Could you please provide some binary/core file as reproducers?


Thanks,
Jan