From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: mark.kettenis@xs4all.nl (Mark Kettenis)
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [rfc] Eliminate write_register from solib-sunos.c
Date: Fri, 15 Jun 2007 16:58:00 -0000 [thread overview]
Message-ID: <200706151658.l5FGwTK3017869@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <200706151646.l5FGkJ4I000248@brahms.sibelius.xs4all.nl> from "Mark Kettenis" at Jun 15, 2007 06:46:19 PM
Mark Kettenis wrote:
> > Date: Mon, 4 Jun 2007 20:53:46 +0200 (CEST)
> > From: "Ulrich Weigand" <uweigand@de.ibm.com>
> >
> > Mark Kettenis wrote:
> >
> > > 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.
> >
> > Did you get around to investigate this?
>
> I started things but didn't finish. And now I've forgotten what
> exactly it was that needed to be tested :(. Can you refresh my mind?
The question was whether that "if (DECR_PC_AFTER_BREAK)" block in
solib-sunos.c was in fact correct, or whether is should be removed.
As Dan suggested, I've in the meantime investigated that issue on
i386-openbsd3.3 under qemu, and found out that this block *is*
correct, because the breakpoint that is hit here was not actually
installed by GDB, but by the dynamic loader itself:
http://sourceware.org/ml/gdb-patches/2007-06/msg00276.html
So, if that's OK with you, I'd like to commit my original patch
that leaves the "if (DECR_PC_AFTER_BREAK)" block in, and simply
replaces the write_register call with write_pc. I've now tested
that patch on my i386-openbsd3.3 setup with no regressions.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-06-15 16:58 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
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 [this message]
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=200706151658.l5FGwTK3017869@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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