Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, pedro@codesourcery.com
Subject: Re: [rfc] Displaced stepping with wrong entry point address
Date: Thu, 04 Sep 2008 19:32:00 -0000	[thread overview]
Message-ID: <20080904193203.GA22456@caradoc.them.org> (raw)
In-Reply-To: <200809041928.m84JS6uq032652@d12av02.megacenter.de.ibm.com>

On Thu, Sep 04, 2008 at 09:28:06PM +0200, Ulrich Weigand wrote:
> > If SPU ever did support displaced stepping (not that this would be
> > terribly useful, but consider some other multi-architecture case),
> > would this be wrong for the SPU side code?
> 
> Yes, of course -- we have different address spaces here, and we need
> to find a location within the address space of the current thread where
> to place the displaced instruction.  No single address would work for
> both PowerPC and SPU code in a combined application.
> 
> But I guess SPU could always install its own callback to handle those
> special cases ...  (just as we install the ON_STACK dummy call location
> method because the AT_ENTRY method doesn't work for combined applications.)

In that case, maybe this is really specific to PowerPC; it sounds like
it won't work for any general multi-architecture target.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-09-04 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-22 17:49 Ulrich Weigand
2008-09-04  1:49 ` [ping] " Ulrich Weigand
2008-09-04 12:15 ` [rfc] " Daniel Jacobowitz
2008-09-04 19:28   ` Ulrich Weigand
2008-09-04 19:32     ` Daniel Jacobowitz [this message]
2008-09-04 20:31       ` Ulrich Weigand
2008-09-05 14:17     ` Mark Kettenis
2008-09-05 16:19       ` [commit, spu] Do not use generic_push_dummy_code 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=20080904193203.GA22456@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    --cc=uweigand@de.ibm.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