From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Pete Delaney <pdelaney@silver-peak.com>
Cc: Andreas Arnez <arnez@linux.vnet.ibm.com>,
"Discussion list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>,
GDB Development <gdb@sourceware.org>
Subject: Re: gdb on KDUMP files
Date: Tue, 21 Oct 2014 05:53:00 -0000 [thread overview]
Message-ID: <20141021055306.GA32003@host2.jankratochvil.net> (raw)
In-Reply-To: <ffc61e9ab6e7423eb7919f0e0828266d@BY2PR04MB173.namprd04.prod.outlook.com>
On Tue, 21 Oct 2014 06:27:32 +0200, Pete Delaney wrote:
> > Nowadays it is only enough to use during configure:
> > --enable-64-bit-bfd
>
> I'll give it a try. I provided O_LARGEFILE to the gdb configure
AC_SYS_LARGEFILE is there since 2009:
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=da2f07f1aa5f8bdeb957df2c520f1d46e6f21bd5
> but I didn't know about this option. With everything going 64-bit these
> days, why isn't it the default. I'm running gdb on a 64 bit machine and
> having trouble reading 64 bit core files. Seems like this should work
> correctly without any additional configure options.
It does. --enable-64-bit-bfd is useful only for 32-bit machines which for
some reason need to deal with 64-bit files.
If there is some problem on 64-bit host it is some other issue than
--enable-64-bit-bfd.
> About 8 years ago I could read a 32 bit KDUMP with gdb
> and, as I recall, each CPU looked like a thread; just like kgdb
> displayed CPU's as threads. I also think embedded JTAG setups
> should do the same.
>
> Are you implying that with:
>
> --enable-64-bit-bfd
>
> I should be able to do that now on a 64-bit machine looking
On 64-bit machine --enable-64-bit-bfd has no effect.
> At 64 bit core dumps and see the back trace for the current
> CPU's at the time of the KDUMP?
I do not deal with kdump files to answer that.
> I found the Documentation/kdump/gdbmacros.txt out of date
> And had to fix them to work. :(
This file is not maintained by this (GDB) project.
Jan
next prev parent reply other threads:[~2014-10-21 5:53 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 [this message]
2014-10-22 0:54 ` Pete Delaney
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=20141021055306.GA32003@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=arnez@linux.vnet.ibm.com \
--cc=crash-utility@redhat.com \
--cc=gdb@sourceware.org \
--cc=pdelaney@silver-peak.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