[Crash-utility] gdb on KDUMP files
Pedro Alves
palves at redhat.com
Thu Oct 30 10:14:37 UTC 2014
On 10/24/2014 01:34 AM, Doug Evans wrote:
> On Tue, Oct 21, 2014 at 5:53 PM, Pete Delaney <pdelaney at silver-peak.com> wrote:
>>> Nowadays it is only enough to use during configure:
>>> --enable-64-bit-bfd
>>
>> I tried
>> configure --enable-64-bit-bfd --enable-largefile
>>
>> And gdb still has problems accessing memory in the KDUMP that the crash-utility can read.
>> For example crash can walk the task list but when the gdb macro tries
>> To access the memory of the second task gdb says it can't access memory.
>
> Hi.
>
> It's not clear from the description that this is a largefile problem.
It sounds likely to be related to points #1 and #2 described earlier in
the discussion:
On 10/17/2014 12:24 PM, Andreas Arnez wrote:
>> > Last time I looked (approx. 1.5 years ago) the main missing pieces were:
>> >
>> > 1. Use of physical addresses (described above)
> I guess this includes the capability to translate virtual to physical
> addresses, using the kernel's page tables?
>
>> > 2. Support for multiple virtual address spaces (for different process
>> > contexts)
> One way of dealing with this might be to represent the different virtual
> address spaces as multiple inferiors.
Thanks,
Pedro Alves
More information about the Crash-utility
mailing list