Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: jan.kratochvil@redhat.com (Jan Kratochvil)
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Fix separate debuginfo files on Cell (do not mask off high  address bits)
Date: Fri, 05 Mar 2010 19:35:00 -0000	[thread overview]
Message-ID: <201003051935.o25JZb2W011064@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20100304203153.GA21129@host0.dyn.jankratochvil.net> from "Jan Kratochvil" at Mar 04, 2010 09:31:53 PM

Jan Kratochvil wrote:
> On Thu, 04 Mar 2010 21:01:01 +0100, Ulrich Weigand wrote:
> > when using the Cell/B.E. combined debugger, separate debug objfiles for
> > SPE executables are currently completely broken.  This is because the
> > new relocation code now masks off high address bits, corrupting the
> > encoded SPU ID in GDB CORE_ADDR values.
> 
> Interesting addr_bit is lower than the valid address width.

Yes, the reason for this is to strip off the SPU ID when converting
address back for output as strings ...

> Yes, it works.  I have considered this masking is just no-op now (only
> possibly with the unresolved negative mips32 addresses reported by Daniel J.).
> 
> 
> No regressions on {x86_64,x86_64-m32,i686}-fedora12-linux-gnu.

Great, thanks for verifying!

I've checked this in to head and 7.1 branch now.

Bye,
Ulrich

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


      parent reply	other threads:[~2010-03-05 19:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 20:01 Ulrich Weigand
2010-03-04 20:32 ` Jan Kratochvil
2010-03-04 20:32   ` Jan Kratochvil
2010-03-05 19:35   ` 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=201003051935.o25JZb2W011064@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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