From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org, ccoutant@google.com, saugustine@google.com
Subject: Re: [RFA 3/3] Initial Fission support, the actual Fission stuff
Date: Fri, 27 Apr 2012 18:29:00 -0000 [thread overview]
Message-ID: <87y5ph2fuu.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22Shvb-tgknNFBye1Up3ALdvYAv8DTex_fmeTOwV0q+oRQ@mail.gmail.com> (Doug Evans's message of "Wed, 18 Apr 2012 21:34:59 -0700")
Doug> IWBN to have an option to make complaints errors, but that is
Doug> problematic as well. For now, my plan is to turn the errors into
Doug> complaints in time.
Radical view follows.
I'm more and more of the opinion that we should just remove all the
complaints.
First, there's evidence that nobody reads them.
There are a few complaints that have been regularly printed for years,
with zero action. (Now, at least one of these is a GCC/GDB/GNU
interpretation of DWARF that is, IMO, baked in and unlikely to change
(the register thing) -- so one may argue that just the bad ones should
be eliminated.)
Second, the complaints are in practice often useless for finding or
reporting any problem. I usually resort to debugging gdb.
Fixable, of course, but seeing as nobody has bothered...
Third, even if the messages were useful, they're still not very good for
ordinary users to understand "why doesn't gdb work". That's because,
unless they are enabled at the moment at which debuginfo is read, they
are just gone.
I think rather than complaints we could get "someone" to fix up
dwarflint instead. This would serve the toolchain development community
better. E.g., we could build the distro with dwarflint checking and fix
the bugs.
Tom
next prev parent reply other threads:[~2012-04-27 18:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-18 19:12 Doug Evans
2012-04-19 5:07 ` Doug Evans
2012-04-27 18:29 ` Tom Tromey [this message]
2012-04-19 10:25 ` Yao Qi
2012-04-19 15:28 ` Doug Evans
2012-04-27 18:38 ` Tom Tromey
2012-04-27 18:20 ` Tom Tromey
2012-04-28 23:59 ` Doug Evans
2012-04-29 9:05 ` Crash regression for gdb.dwarf2/dw2-inheritance.exp [Re: [RFA 3/3] Initial Fission support, the actual Fission stuff] Jan Kratochvil
2012-04-30 0:06 ` Doug Evans
2012-04-30 2:07 ` Jan Kratochvil
2012-04-30 14:30 ` Doug Evans
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=87y5ph2fuu.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ccoutant@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=saugustine@google.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