public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: ac131313@redhat.com, gdb@sources.redhat.com
Subject: Re: More debug info test directories?
Date: Tue, 19 Aug 2003 17:57:00 -0000	[thread overview]
Message-ID: <200308191757.h7JHvju2022432@duracef.shout.net> (raw)

> What do people think of additional debug info directories vis:
> 
> gdb.dw2
> gdb.dw1

Sounds good to me.

Why not call them gdb.dwarf-1 and gdb.dwarf-2?  Oh, because of
the 8.3 uniqueness requirement.  Sigh.

Well, you could re-visit the issue of dwarf-1 support first.  It may be
too early to remove dwarf-1 support, but I think it's okay to not add
any more dwarf-1 tests.  The existing test suite gave, like, 50 ERRORs
and 3500 FAILs the last time I ran it.  And the only dwarf-1 compilers
I know about are Absoft, Diab, and SCO's version of gcc.

Michael C

             reply	other threads:[~2003-08-19 17:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-19 17:57 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-08-19 13:24 Andrew Cagney
2003-08-19 13:28 ` Daniel Jacobowitz
2003-08-28 20:16   ` 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=200308191757.h7JHvju2022432@duracef.shout.net \
    --to=mec@shout.net \
    --cc=ac131313@redhat.com \
    --cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).