From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB PR categories
Date: Thu, 26 Sep 2002 14:17:00 -0000 [thread overview]
Message-ID: <ro1smzwmowr.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3D937699.3020502@redhat.com>
On Thu, 26 Sep 2002 17:05:29 -0400, Andrew Cagney <ac131313@redhat.com> said:
>> If you're going to create so many categories, how about one for
>> each debugging format as well?
> I think it might confuse things. The only way the average user is
> going to spot a symtab bug is by GDB printing out:
> internal-error: symtab.c: .....
> :-)
That's a good point, and one that I hadn't considered. Having said
that, the categories are more for our benefit, not for users'
benefits, so as long as we don't mind moving PR's to an appropriate
category once they've been analyzed, then debugging format-specific
categories could be useful.
But probably in practice there would be few enough such bugs that
having a generic 'symtab' category is good enough.
> (BTW, anyone know the story with ``-'' in categories. I think
> fernando indicated that it wasn't valid but the online docs
> (http://www.gnu.org/software/gnats/ uses that in the examples.)
Wasn't Fernando complaining about "-" in categories for the testsuite?
Something about argument passing and runtest?
Though now that I look at the actual thread, I'm confused.
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2002-09-26 21:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 11:16 Andrew Cagney
2002-09-26 12:48 ` David Carlton
2002-09-26 14:05 ` Andrew Cagney
2002-09-26 14:08 ` Daniel Jacobowitz
2002-09-26 14:17 ` David Carlton [this message]
2002-09-26 13:58 ` Jim Blandy
2002-09-26 14:08 ` Elena Zannoni
2002-09-28 9:59 ` 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=ro1smzwmowr.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--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