Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: uweigand@de.ibm.com
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [rfc] Eliminate write_register from solib-sunos.c
Date: Mon, 14 May 2007 15:15:00 -0000	[thread overview]
Message-ID: <200705141515.l4EFFOHF015937@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <200705141500.l4EF0CH3027553@d12av02.megacenter.de.ibm.com> 	(uweigand@de.ibm.com)

> Date: Mon, 14 May 2007 17:00:12 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> 
> Daniel Jacobowitz wrote:
> > On Sat, May 12, 2007 at 02:31:13AM +0200, Ulrich Weigand wrote:
> > > Hello,
> > > 
> > > solib-sunos.c has a place where it adjusts the PC by DECR_PC_AFTER_BREAK.
> > > Unlike all other places to do so, it uses write_register (PC_REGNUM ...).
> > > 
> > > As I'm trying to eliminate write_register, I'd like to get rid of this.
> > > The following patch replaces the write_register call by write_pc.
> > > 
> > > Is this OK?
> > 
> > I noticed this call last week.  I'm not sure if any platform using
> > solib-sunos.c even triggers it... but if they do, I think it's
> > decrementing the PC twice.  Didn't infrun take care of it?
> 
> Hmm, good point.  I think infrun *should* take care of it; solib-sunos.c
> calls wait_for_inferior, which calls handle_inferior_event, which calls
> adjust_pc_after_break.
> 
> Interestingly enough, it would appear that none of the Solaris targets
> are actually using solib-sunos.o.  The only references I can find are
> in various bsd *native* target's .mh files.

This is the shared library support for the old SunOS 4.x (aka Solaris
1.x).  Solaris 2.x (aka SunOS 5.x) uses SVR4-style shared libraries.

> In fact, this is very weird as those same bsd targets have solib-svr4.o
> in their .mt files.  Which one is getting used in that case?  I'll try
> to find out what's going on here ...

There are some a.out BSD targets that use solib-sunos.o.  In
particular OpenBSD/m68k still uses it.  Interestingly enough, that
target sets DECR_PC_AFTER_BREAK to 2.  I'll fire up my Quadra 800 and
investigate somewhere later this week.

Mark


  reply	other threads:[~2007-05-14 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-12  0:31 Ulrich Weigand
2007-05-13 23:55 ` Daniel Jacobowitz
2007-05-14 15:01   ` Ulrich Weigand
2007-05-14 15:15     ` Mark Kettenis [this message]
2007-05-14 20:53       ` Ulrich Weigand
2007-06-04 18:53       ` Ulrich Weigand
2007-06-15 16:46         ` Mark Kettenis
2007-06-15 16:58           ` Ulrich Weigand
2007-06-15 21:22             ` Mark Kettenis
2007-06-15 21:28             ` Daniel Jacobowitz
2007-06-15 22:13               ` Ulrich Weigand
2007-05-14 15:21     ` Daniel Jacobowitz
2007-05-14 20:28       ` 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=200705141515.l4EFFOHF015937@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --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