From: Eli Zaretskii <eliz@is.elta.co.il>
To: ac131313@cygnus.com
Cc: gdb-patches@sources.redhat.com, davea@quasar.engr.sgi.com
Subject: Re: [RFA] Support for GDB on SGI Irix 6.x
Date: Wed, 06 Jun 2001 23:25:00 -0000 [thread overview]
Message-ID: <200106070627.JAA28491@is.elta.co.il> (raw)
In-Reply-To: <3B1E5DB2.90209@cygnus.com>
> Date: Wed, 06 Jun 2001 12:43:30 -0400
> From: Andrew Cagney <ac131313@cygnus.com>
> X-Accept-Language: en
> Cc: gdb-patches@sources.redhat.com,
> David B Anderson <davea@quasar.engr.sgi.com>
>
> > This is a followup for
> >
> > http://sources.redhat.com/ml/gdb-patches/2001-05/msg00341.html
> >
> > where I posted a set of patches to make GDB support n32 executables on
> > SGI Irix. Since then, David Anderson reported that, with a minor
> > change in irix6.mh, GDB builds and works on SGI for him as well.
> >
> > So I would like to commit these changes (reproduced below). Any
> > objections?
[...]
> No.
Just to be sure I understand: is that a "No" to my question "Any
objections [to committing this]?", or do you mean you are rejecting
the patches?
> PS: For those that are wondering. Eli's code contains things like:
>
> > +#undef REGISTER_BYTES
> > +#define REGISTER_BYTES (MIPS_NUMREGS * 8 + (NUM_REGS - MIPS_NUMREGS) * MIPS_REGSIZE)
> >
>
> yet MIPS is ment to be multi-arch. MIPS is actually multi-arch except
> for the register buffer and a few other things.
Correction: quite a few of other things. For example, the ABI type is
not automatically determined from the debuggee, AFAICS. This is a major
roadblock for Irix, with its multitude of different ABIs.
> To safely fix this, I think remote.c would need to be changed so that it
> allowed:
>
> o several different pre-defined G packet
> layouts for a single architecture
>
> o a CLI mechanism that allows the user
> to either select a pre-defiend G packet
> format _OR_ define their own custom
> G packet format.
I hope this isn't going to be a prerequisite for committing my
patches. Right now, GDB is unusable on Irix 6.x, since it aborts at
startup due to use of incorrect layout of the register file. The
patches I sent make it work for debugging n32 binaries, which I think
is a reason good enough to get it in, even though it isn't multi-arch.
next prev parent reply other threads:[~2001-06-06 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 1:12 Eli Zaretskii
2001-06-06 9:43 ` Andrew Cagney
2001-06-06 23:25 ` Eli Zaretskii [this message]
2001-06-07 9:21 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2001-05-17 7:44 Eli Zaretskii
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=200106070627.JAA28491@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=ac131313@cygnus.com \
--cc=davea@quasar.engr.sgi.com \
--cc=gdb-patches@sources.redhat.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