public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Jon Zhou <Jon.Zhou@jdsu.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: support biarch gcore?
Date: Mon, 05 Jul 2010 07:12:00 -0000	[thread overview]
Message-ID: <20100705071235.GA26137@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <4A6A2125329CFD4D8CC40C9E8ABCAB9F24987E52BB@MILEXCH2.ds.jdsu.net>

On Mon, 05 Jul 2010 06:52:37 +0200, Jon Zhou wrote:
> Regarding this case, does the current release solve it ? I just tried the
> patch but looks it doesn't work

Issue is tracked at:
	amd64 gdb generates corrupted 32bit core file
	http://sourceware.org/bugzilla/show_bug.cgi?id=11467

There was a patchset by H.J.Lu but it did not make it in FSF GDB:
	PATCH: PR corefiles/11467: amd64 gdb generates corrupted 32bit core file
	http://sourceware.org/ml/gdb-patches/2010-04/msg00315.html
with the last mail of this thread:
	http://sourceware.org/ml/gdb-patches/2010-04/msg00427.html
	> Please stop sending diffs until you understand how the code is
	> supposed to work.

The Fedora patch
	http://cvs.fedoraproject.org/viewvc/rpms/gdb/devel/gdb-6.5-gcore-i386-on-amd64.patch?content-type=text%2Fplain&view=co

will be rebased or replaced by H.J.Lu's one for gdb-7.2-pre by 2010-07-27.


Thanks,
Jan


> References: <4A25DE879BC24E8DAEAEBD722E363025@igor>
> In-Reply-To: <4A25DE879BC24E8DAEAEBD722E363025@igor>

Please do not reply to the existing mail "Examining copied stack contents"
when you start a new thread.

  reply	other threads:[~2010-07-05  7:12 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 [this message]
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
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=20100705071235.GA26137@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=Jon.Zhou@jdsu.com \
    --cc=gdb@sourceware.org \
    /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).