From: Kevin Buettner <kevinb@redhat.com>
To: Jimi Xenidis <jimix@watson.ibm.com>, Kevin Buettner <kevinb@redhat.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
gdb-patches@sources.redhat.com,
Andrew Cagney <ac131313@redhat.com>
Subject: Re: AHAH! Re: Patch to eliminate SOFTWARE_SINGLE_STEP from ppc Was: Powerpc and software single step
Date: Tue, 09 Sep 2003 16:15:00 -0000 [thread overview]
Message-ID: <1030909161519.ZM20803@localhost.localdomain> (raw)
In-Reply-To: Jimi Xenidis <jimix@watson.ibm.com> "AHAH! Re: Patch to eliminate SOFTWARE_SINGLE_STEP from ppc Was: Powerpc and software single step" (Sep 9, 11:30am)
On Sep 9, 11:30am, Jimi Xenidis wrote:
> >>>>> "KB" == Kevin Buettner <kevinb@redhat.com> writes:
>
> KB> Would you mind doing some tracing to figure out why wrapping it
> KB> with a test for AIX wasn't necessary? The fact that you didn't
> KB> need a test suggests that there's a bug somewhere else...
>
> gdb/config/powerpc/tm-ppc-eabi.h defines the predicate
> SOFTWARE_SINGLE_STEP_P() as 0 but does not define
> SOFTWARE_SINGLE_STEP() at all. If I remove this def then all works as
> expected.
>
> So what should the AIX test be? possible canidates are:
> ? if (info.osabi != GDB_OSABI_LINUX)
> * Not sure if this is good enough for the PPC-EABI or anyone else
> ? if (from_xcoff_exec)
>
> or clear it to NULL in ppclinux and eabi.
>
> thoughts?
Ideally, we'd have a GDB_OSABI_AIX constant to use for the test.
It'd also be nice if (eventually) the generic vs AIX specific code
were split into two separate files. At first, I was thinking that AIX
specific code ought to move to a different file, but now I think it makes
more sense to do it the other way around, i.e, move the generic PPC
(and Power) code to its own file and let rs6000-tdep.c contain only
AIX specific code in much the same way that ppc-linux-tdep.c contains
only linux specific code.
Kevin
next prev parent reply other threads:[~2003-09-09 16:15 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-12 22:31 Jimi Xenidis
2003-08-19 17:55 ` Kevin Buettner
2003-08-19 19:05 ` Jimi Xenidis
2003-08-19 19:13 ` Daniel Jacobowitz
2003-08-19 22:32 ` Jimi Xenidis
2003-08-20 2:30 ` Daniel Jacobowitz
2003-08-20 2:57 ` Jimi Xenidis
2003-08-20 3:09 ` Daniel Jacobowitz
2003-08-20 3:21 ` Jimi Xenidis
2003-08-20 13:07 ` Daniel Jacobowitz
2003-08-20 13:54 ` Jimi Xenidis
2003-08-20 15:51 ` Andrew Cagney
2003-08-20 16:02 ` Jimi Xenidis
2003-08-21 3:48 ` Andrew Cagney
2003-08-22 13:17 ` Jimi Xenidis
2003-08-22 15:54 ` Andrew Cagney
2003-08-22 17:32 ` Jimi Xenidis
2003-08-22 18:20 ` Andrew Cagney
2003-09-08 18:58 ` Patch to eliminate SOFTWARE_SINGLE_STEP from ppc Was: " Jimi Xenidis
2003-09-08 19:00 ` Daniel Jacobowitz
2003-09-08 20:17 ` Jimi Xenidis
2003-09-08 20:20 ` Daniel Jacobowitz
2003-09-08 21:22 ` Jimi Xenidis
2003-09-08 22:01 ` Kevin Buettner
2003-09-09 10:30 ` Jimi Xenidis
2003-09-09 15:30 ` AHAH! " Jimi Xenidis
2003-09-09 16:15 ` Kevin Buettner [this message]
2003-09-09 17:01 ` Jimi Xenidis
2003-09-09 17:55 ` Kevin Buettner
2003-09-09 22:01 ` PATCH: Re: AHAH! Re: Patch to eliminate SOFTWARE_SINGLE_STEP Jimi Xenidis
2003-09-10 1:24 ` Kevin Buettner
2003-10-10 2:40 ` Andrew Cagney
2003-08-20 2:30 ` Powerpc and software single step Andrew Cagney
2003-08-20 2:33 ` Daniel Jacobowitz
2003-08-21 14:01 ` Andrew Cagney
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=1030909161519.ZM20803@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimix@watson.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