From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: jkj@sco.com, shebs@apple.com
Cc: cagney@gnu.org, ezannoni@redhat.com, gdb@sources.redhat.com,
jimb@redhat.com, mec.gnu@mindspring.com,
nathanw@wasabisystems.com
Subject: Re: Phasing out Dwarf 1?
Date: Wed, 05 May 2004 05:03:00 -0000 [thread overview]
Message-ID: <20040505050212.1CF744B104@berman.michael-chastain.com> (raw)
Stan Shebs writes:
> But how is it going to get tested? Experience shows that untested parts
> of GDB bitrot pretty quickly, and without any volunteers to let us know
> when things break and/or fix them when they do, the claim of support
> is just misleading to users.
On this subject, the last time I tried dwarf-1 with the gdb test suite,
I got 46 ERROR, 39 UNRESOLVED, and 3463 FAIL. This was in February 2003.
http://sources.redhat.com/ml/gdb-patches/2003-02/msg00293.html
IIRC, the test suite took about nine hours to run, compared to fifteen
minutes for dwarf-2 or stabs+.
I don't know if this is systemic failure in the test suite or
systemic failure in gdb.
Michael C
next reply other threads:[~2004-05-05 5:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 5:03 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-06 15:00 Michael Elizabeth Chastain
2004-05-07 1:19 ` Andrew Cagney
2004-05-05 22:01 Michael Elizabeth Chastain
2004-05-06 14:02 ` Andrew Cagney
2004-05-06 20:11 ` Mark Kettenis
2004-05-05 21:33 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-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
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=20040505050212.1CF744B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jkj@sco.com \
--cc=nathanw@wasabisystems.com \
--cc=shebs@apple.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