From: Andrew Cagney <cagney@gnu.org>
To: "Nathan J. Williams" <nathanw@wasabisystems.com>
Cc: Michael Elizabeth Chastain <mec.gnu@mindspring.com>,
ezannoni@redhat.com, gdb@sources.redhat.com, jimb@redhat.com
Subject: Re: Phasing out Dwarf 1?
Date: Mon, 10 May 2004 21:09:00 -0000 [thread overview]
Message-ID: <409FEF69.7080904@gnu.org> (raw)
In-Reply-To: <mtud65kjf0t.fsf@all-night-tool.mit.edu>
> Andrew Cagney <cagney@gnu.org> writes:
>
>
>>> (we might also determine that such systems require an ISO-C compiler
>>> (e.g., GCC) to build GDB and hence argue that GDB can assume dwarf-2
>>> is present.)
>
>
> This seems like a poor argument. The availibility and suitability of
> modern GCC for building GDB does not imply that modern GCC will be
> suitable for building the application to be debugged.
For the systems of concern here they have old compilers, and equally old
shipped debuggers. While a current GDB might work in theory, in reality
it just isn't worth the effort of finding out - remember step-1 is
somehow build/test an ISO-C compiler.
Andrew
next prev parent reply other threads:[~2004-05-10 21:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 15:56 Michael Elizabeth Chastain
2004-05-04 15:37 ` Andrew Cagney
2004-05-04 17:09 ` Nathan J. Williams
2004-05-04 17:19 ` Kean Johnston
2004-05-05 0:28 ` Stan Shebs
2004-05-05 5:57 ` Jim Blandy
2004-05-10 21:09 ` Andrew Cagney [this message]
2004-05-05 5:03 Michael Elizabeth Chastain
2004-05-05 5:24 Michael Elizabeth Chastain
2004-05-05 14:31 ` Andrew Cagney
2004-05-05 16:05 ` Kean Johnston
2004-05-05 18:30 ` Stan Shebs
2004-05-05 18:53 ` Kean Johnston
2004-05-05 21:33 Michael Elizabeth Chastain
2004-05-05 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
2004-05-06 15:00 Michael Elizabeth Chastain
2004-05-07 1:19 ` 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=409FEF69.7080904@gnu.org \
--to=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=nathanw@wasabisystems.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