public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
To: ac131313@redhat.com
Cc: mec@shout.net, jkj@sco.com, eflash@gmx.net, gdb@sources.redhat.com
Subject: Re: Deprecate dwarf and mdebug support, delete nlm?
Date: Sat, 10 May 2003 09:25:00 -0000	[thread overview]
Message-ID: <2110-Sat10May2003122057+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3EBBDBF3.6030607@redhat.com> (message from Andrew Cagney on Fri, 09 May 2003 12:48:51 -0400)

> Date: Fri, 09 May 2003 12:48:51 -0400
> From: Andrew Cagney <ac131313@redhat.com>
> 
> > mec> Are there still a lot of SCO users with gcc 2?
> > kj> HUGE numbers. It's the currently "officially supported" version
> > kj> that we give our customers. Until 3.3 we haven't really felt GCC
> > kj> 3 was ready for primetime. In fact the next "oficially supported"
> > kj> version will be 3.4.
> 
> > Okay, that means we have to keep dwarf 1 for another 6-12 months
> > at least.  Rats.
> 
> I don't know ....

My vote is to retain DWARF 1 until SCO switches to GCC 3.x as their
official version.  I think otherwise we would be unfairly punishing
SCO users.  I agree with Kean that a solid compiler is much more
important that a debugger, so most users will not upgrade GCC just
because GDB wants them to.  OTOH, those SCO users who do use GDB
should be able to benefit from the new GDB features.

> Yes.  There is no such thing as free beer.  Someone, eventually, ends up 
> paying for it.

Let's ask the SCO developers to pay at least part of that price.  In
fact, Kean already volunteered, so that issue appears to be taken care
of.

> This has come up before.  The GDB 4 to 5 transition occured due to a 
> switch to ISO C.  People with a K&R compiler needing to either download 
> GCC, or GDB 4.x.

That's a totally different beer ;-) The compiler used to build GDB is
not teh same as the compiler used to build production software.  One
could install a newer GCC, compile GDB, and then use the older GCC for
development.  Or one could download binary packages of GDB someone
else built.  It's much easier to solve this kind of problems than the
one SCO users will face if we drop DWARF 1 now.

  reply	other threads:[~2003-05-10  9:25 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09 15:47 Michael Elizabeth Chastain
2003-05-09 16:37 ` Kean Johnston
2003-05-09 17:03   ` Andrew Cagney
2003-05-09 16:48 ` Andrew Cagney
2003-05-10  9:25   ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-09 15:22 Michael Elizabeth Chastain
2003-05-09 15:34 ` Kean Johnston
2003-05-09  8:10 Armin Diehl
     [not found] <200305082242.h48MgQH06975@mx1.redhat.com>
2003-05-09  0:02 ` Elena Zannoni
     [not found] <E19Duaa-0005kw-00@monty-python.gnu.org>
2003-05-08 23:42 ` Andrew Cagney
2003-05-09 15:12   ` Kean Johnston
2003-05-08 23:14 Günter Knauf
2003-05-08 22:52 Ulrich Neumann
2003-05-09  0:09 ` Elena Zannoni
2003-05-08 22:42 Günter Knauf
2003-05-04 16:08 Michael Elizabeth Chastain
2003-05-05 15:23 ` Tim Combs
2003-05-05 17:30   ` Andrew Cagney
2003-05-05 17:49     ` Daniel Berlin
2003-05-04  6:10 Michael Elizabeth Chastain
2003-05-04  6:43 ` Daniel Berlin
2003-05-04  4:41 Andrew Cagney
2003-05-04 15:41 ` Daniel Jacobowitz
2003-05-04 19:52 ` Elena Zannoni
2003-05-05 17:37   ` Andrew Cagney
2003-05-05  0:14 ` Andrew Cagney
2003-05-05  3:58 ` Joel Brobecker
2003-05-05 17:24 ` Jim Blandy

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=2110-Sat10May2003122057+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=ac131313@redhat.com \
    --cc=eflash@gmx.net \
    --cc=gdb@sources.redhat.com \
    --cc=jkj@sco.com \
    --cc=mec@shout.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).