From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: Jon.Zhou@jdsu.com (Jon Zhou)
Cc: mark.kettenis@xs4all.nl (Mark Kettenis),
jan.kratochvil@redhat.com (jan.kratochvil@redhat.com),
gdb@sourceware.org (gdb@sourceware.org),
gdb-patches@sourceware.org (gdb-patches@sourceware.org)
Subject: Re: support biarch gcore?
Date: Thu, 08 Jul 2010 11:17:00 -0000 [thread overview]
Message-ID: <201007081117.o68BHVtV026786@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <4A6A2125329CFD4D8CC40C9E8ABCAB9F249888AB28@MILEXCH2.ds.jdsu.net> from "Jon Zhou" at Jul 07, 2010 07:33:59 PM
Jon Zhou wrote:
> One more question
>
> The patch is enable gdb to read the coredump generated by gcore
> Or enable gcore to generate a readable coredump
> Or both?
The patch fixes the gcore command to generate a coredump in the
proper 32-bit format.
Reading in a 32-bit format coredump did already work correctly
before (e.g. a coredump generated by the kernel).
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2010-07-08 11:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 10:48 Examining copied stack contents Martin Schröder
2010-07-05 4:54 ` support biarch gcore? Jon Zhou
2010-07-05 7:12 ` Jan Kratochvil
2010-07-05 11:55 ` Mark Kettenis
2010-07-06 20:48 ` Ulrich Weigand
2010-07-06 21:29 ` Mark Kettenis
2010-07-07 12:30 ` Ulrich Weigand
2010-07-08 2:35 ` Jon Zhou
2010-07-08 11:17 ` Ulrich Weigand [this message]
2010-07-08 4:47 ` H.J. Lu
2010-07-08 5:05 ` H.J. Lu
2010-07-08 11:15 ` Ulrich Weigand
2010-07-08 13:52 ` H.J. Lu
2010-07-21 22:45 ` Joseph S. Myers
2010-07-05 18:50 ` Examining copied stack contents Petr Hluzín
2010-07-05 20:18 ` Martin Schröder
2010-07-05 20:27 ` Joel Brobecker
2010-07-07 17:29 ` Martin Schröder
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=201007081117.o68BHVtV026786@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=Jon.Zhou@jdsu.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).