public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
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: Mon, 05 Nov 2007 18:05:00 -0000	[thread overview]
Message-ID: <200711051805.lA5I5Jrk026631@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20071102011905.ACF714D04C0@magilla.localdomain> from "Roland McGrath" at Nov 01, 2007 06:19:05 PM

Hi Roland,

> Hi, Ulrich.  Thanks for bringing these problems to my attention.
> I have fixed them in "upstream" utrace (http://redhat.com/~roland/utrace/)
> and those changes will appear in Fedora update kernels before too long.
> I've also added regression tests for them to the ptrace-tests suite
> (http://sourceware.org/systemtap/wiki/utrace/tests).

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?)

> These are not gdb issues at all, just Fedora kernel bugs.  (Any
> regression in ptrace ABI behavior of this sort from vanilla Linux kernels
> is an unintended bug.)  The normal method is to file Fedora kernel bugs
> via https://bugzilla.redhat.com/.  Since you know it's an issue with the
> utrace code, the feedback is always appreciated if you want post to the
> utrace-devel@redhat.com mailing list about any such issue.

Thanks, I'll do that if I find further utrace-related problems.

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com

  reply	other threads:[~2007-11-05 18:05 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 [this message]
2007-11-08  0:07     ` Roland McGrath
2007-11-09 19:21       ` Ulrich Weigand

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=200711051805.lA5I5Jrk026631@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).