From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: roland@redhat.com (Roland McGrath)
Cc: gdb@sourceware.org
Subject: Re: Fedora utrace changes break PPC GDB
Date: Fri, 09 Nov 2007 19:21:00 -0000 [thread overview]
Message-ID: <200711091921.lA9JLLUl018188@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071108000637.A81E04D0564@magilla.localdomain> from "Roland McGrath" at Nov 07, 2007 04:06:37 PM
Roland McGrath wrote:
> > Thanks for the quick fix! I'll verify that it works for me as soon as
> > the patches are included in Fedora. (I'm assuming it is too late for
> > them to get into Fedora 8 at this point, right?)
>
> Yeah, that ship sailed a few days ago. But there is kernel built already
> (koji.fedoraproject.org) that will be an f8-updates kernel soon, I'd guess
> within a couple of days.
Thanks again! I've now verified that the ptrace interface works as expected
again with kernel-2.6.23.1-48.fc8. Unfortunately I ran in a number of separate
issues that caused watchpoints to remain broken on my test system:
- A GDB PPC regression that came in recently.
This is fixed by http://sourceware.org/ml/gdb-patches/2007-11/msg00202.html
- A Cell/B.E. specific kernel bug (the DABRX register is not enabled).
I've got a hack to work around this, and am currently working with the
Cell kernel team to get a proper fix upstream.
With those two problems fixed in addition to the utrace fix, the watchpoint
related test cases in the GDB test suite pass again.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-11-09 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 21:21 Ulrich Weigand
2007-11-02 1:19 ` Roland McGrath
2007-11-05 18:05 ` Ulrich Weigand
2007-11-08 0:07 ` Roland McGrath
2007-11-09 19:21 ` Ulrich Weigand [this message]
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=200711091921.lA9JLLUl018188@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=gdb@sourceware.org \
--cc=roland@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).