Re: gdb on KDUMP files

On Tue, Oct 21, 2014 at 5:53 PM, Pete Delaney <[email protected]> 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.
As an experiment, what happens if you build with CFLAGS="-g -O2
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE" ?
[not all of these macros may be necessary, configure should be
defining _FILE_OFFSETS_BITS=64, THIS IS JUST AN EXPERIMENT]

>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of Jan Kratochvil
> Sent: Friday, October 17, 2014 4:56 AM
> To: Andreas Arnez
> Cc: Discussion list for crash utility usage, maintenance and development; GDB Development
> Subject: Re: gdb on KDUMP files
>
> On Fri, 17 Oct 2014 13:24:01 +0200, Andreas Arnez wrote:
>> >   4. Ability to use 64-bit files on 32-bit platforms (to handle PAE)
>
> This was:
>         https://bugzilla.redhat.com/show_bug.cgi?id=457187
> Nowadays it is only enough to use during configure:
>         --enable-64-bit-bfd
>
>
> Additionally Fedora is carrying for Linux kernel support:
>         http://pkgs.fedoraproject.org/cgit/gdb.git/tree/gdb-6.5-bz203661-emit-relocs.patch
> dsicussed in the thread:
>         https://sourceware.org/ml/gdb/2006-08/msg00137.html
>
>
> Jan