public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/11467] amd64 gdb generates corrupted 32bit core file
Date: Fri, 02 Apr 2010 14:25:00 -0000 [thread overview]
Message-ID: <20100402142538.26034.qmail@sourceware.org> (raw)
In-Reply-To: <20100402134748.11467.hjl.tools@gmail.com>
------- Additional Comments From jan dot kratochvil at redhat dot com 2010-04-02 14:25 -------
There are many patches in Fedora planned to be submitted for FSF GDB.
I am not confident the patch is currently in a shape for upstream, I would need
to check if it would not be better integrated putting part of it in bfd/ etc.
If you are confident the current form of the patch is right for FSF GDB HEAD
feel free to submit it. Working on other issues now. RH recently already
upstreamed (by different implementations) many RH C++ patches or the PIE patch.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=11467
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-04-02 14:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 13:47 [Bug corefiles/11467] New: " hjl dot tools at gmail dot com
2010-04-02 13:54 ` [Bug corefiles/11467] " jan dot kratochvil at redhat dot com
2010-04-02 13:54 ` jan dot kratochvil at redhat dot com
2010-04-02 14:13 ` hjl dot tools at gmail dot com
2010-04-02 14:25 ` jan dot kratochvil at redhat dot com [this message]
2010-04-10 22:31 ` hjl dot tools at gmail dot com
2010-04-13 12:56 ` hjl dot tools at gmail dot com
2010-05-03 16:20 ` hjl dot tools at gmail dot com
2010-05-07 17:50 ` jan dot kratochvil at redhat dot com
2010-05-07 17:54 ` jan dot kratochvil at redhat dot com
2010-07-08 13:55 ` hjl dot tools at gmail dot com
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=20100402142538.26034.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@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).