From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, Joel Brobecker <brobecker@gnat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] minimal symbols on mips-irix and overlapping CUs...
Date: Tue, 18 Nov 2003 00:25:00 -0000 [thread overview]
Message-ID: <3FB966EA.5060500@redhat.com> (raw)
In-Reply-To: <20031117233542.GA12125@nevyn.them.org>
FYI, from nodebug.exp:
# Irix5, even though it is ELF, counts as "ecoff" because it
# encapsulates ecoff debugging info in a .mdebug section.
# Irix6 gcc omits no debug info at all for static functions and
# variables, so all tests involving statics fail.
next prev parent reply other threads:[~2003-11-18 0:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 22:39 Joel Brobecker
2003-11-17 23:35 ` Daniel Jacobowitz
2003-11-18 0:25 ` Andrew Cagney [this message]
2003-11-18 0:28 ` Daniel Jacobowitz
2003-11-18 1:25 ` Joel Brobecker
2003-11-22 18:54 ` Andrew Cagney
2003-11-23 1:14 ` Daniel Jacobowitz
2003-11-23 4:04 ` Joel Brobecker
2003-11-18 1:24 ` Joel Brobecker
2003-11-18 1:33 ` Daniel Jacobowitz
2003-11-23 20:00 David Anderson
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=3FB966EA.5060500@redhat.com \
--to=ac131313@redhat.com \
--cc=brobecker@gnat.com \
--cc=drow@mvista.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