Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: 5.1 PATCH: Allow gdb to link on mips-sgi-irix5.3
Date: Fri, 27 Jul 2001 04:55:00 -0000	[thread overview]
Message-ID: <15201.22181.545436.593017@xayide.TechFak.Uni-Bielefeld.DE> (raw)
In-Reply-To: <9743-Fri27Jul2001120548+0300-eliz@is.elta.co.il>

Eli Zaretskii writes:

> Is there any reason why you didn't use mips-sgi-irix6 configuration?
> Since you want to debug on Irix 6.x, that sounds like The Right Way,
> no?

I had supposed (incorrectly, it seems) that, like GCC, GDB only supported
either the O32 (in the IRIX 5 configuration) or N32/N64 (in the IRIX 6
configuration) ABIs.

> The CVS version should build and work when configured as
> mips-sgi-irix6, but I only tested that with n32 and -64 executables
> (the latter is _known_ to be broken for now, see NEWS, but GDB never
> supported -64 anyway).  So it's possible that o32 has some issues, but
> I did try not to break it when I fixed n32 support on Irix 6.

While a mips-sgi-irix6.2 configuration is able to debug the O32-with-stabs
hello-gcc that fails in the mips-sgi-irix5.3 configuration, the
O32-with-mdebug binary still triggers the same internal error reported with
my patch.

	Rainer

-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University

Email: ro@TechFak.Uni-Bielefeld.DE


  reply	other threads:[~2001-07-27  4:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-26 14:42 Rainer Orth
2001-07-26 15:13 ` Elena Zannoni
2001-07-27  2:06 ` Eli Zaretskii
2001-07-27  4:55   ` Rainer Orth [this message]
2001-07-27  7:25     ` Eli Zaretskii
2001-07-27  7:28       ` Rainer Orth
2001-07-30 13:14 Rainer Orth
2001-07-31  1:40 ` Eli Zaretskii
2001-07-31  8:19   ` Andrew Cagney
2001-10-14 13:59     ` 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=15201.22181.545436.593017@xayide.TechFak.Uni-Bielefeld.DE \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=eliz@is.elta.co.il \
    --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