From: Pete Delaney <pdelaney@silver-peak.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>,
Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: "Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>,
GDB Development <gdb@sourceware.org>,
"Pete Delaney" <pdelaney@silver-peak.com>,
Piet Delaney <piet.delaney@gmail.com>
Subject: RE: gdb on KDUMP files
Date: Wed, 22 Oct 2014 00:54:00 -0000 [thread overview]
Message-ID: <edf4b8070b6c431e832841ebfb03ea84@BY2PR04MB173.namprd04.prod.outlook.com> (raw)
In-Reply-To: <20141017115550.GA7123@host2.jankratochvil.net>
> 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.
-piet
--
Pete/Piet Delaney
O: +1 408 935-1813
C: +1 408 646-8557
H: +1 408 243-8872
Home Email: piet.delaney@gmail.com
-----Original Message-----
From: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] 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
next prev parent reply other threads:[~2014-10-22 0:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b3a5a177772a47e8bf740e3422befa6a@BY2PR04MB173.namprd04.prod.outlook.com>
[not found] ` <20141002102700.3eba84a5@suse.cz>
2014-10-17 11:24 ` Andreas Arnez
2014-10-17 11:55 ` Jan Kratochvil
[not found] ` <ffc61e9ab6e7423eb7919f0e0828266d@BY2PR04MB173.namprd04.prod.outlook.com>
2014-10-21 5:53 ` Jan Kratochvil
2014-10-22 0:54 ` Pete Delaney [this message]
2014-10-24 0:34 ` Doug Evans
2014-10-30 10:14 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=edf4b8070b6c431e832841ebfb03ea84@BY2PR04MB173.namprd04.prod.outlook.com \
--to=pdelaney@silver-peak.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=crash-utility@redhat.com \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=piet.delaney@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox