Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc][1/13] Eliminate read_register: write_register in 	solib-sunos.c
Date: Tue, 12 Jun 2007 13:45:00 -0000	[thread overview]
Message-ID: <20070612134525.GB7815@caradoc.them.org> (raw)
In-Reply-To: <200706072057.l57KvBBL019253@d12av02.megacenter.de.ibm.com>

On Thu, Jun 07, 2007 at 10:57:11PM +0200, Ulrich Weigand wrote:
> Hello,
> 
> this patch eliminates the use of write_register in solib-sunos.c.
> As discussed when I've originally posted the patch, the whole
> "if (DECR_PC_AFTER_BREAK)" block is questionable, and the correct
> solution might be to completely remove it.

I'd prefer that - unfortunately I believe Mark is travelling now
so it may be a while before he can test it.  I suppose that if you're
feeling really brave, you could try running OpenBSD in aranym.
Actually, i386-openbsd3.3 in qemu would probably be much easier.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-06-12 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 20:57 Ulrich Weigand
2007-06-12 13:45 ` Daniel Jacobowitz [this message]
2007-06-13 22:11   ` 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=20070612134525.GB7815@caradoc.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@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