From: Andrew Cagney <ac131313@redhat.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Re: Question about ARI
Date: Wed, 07 May 2003 16:07:00 -0000 [thread overview]
Message-ID: <3EB92F56.10209@redhat.com> (raw)
In-Reply-To: <09fe01c313e2$6a5ca920$0202040a@catdog>
> I'm really impressed with this tool. Can anyone tell me any more about it?
> I wouldn't mind seeing something like this running on our internal stuff.
See the adminstration section of http://sources.redhat.com/gdb/current/
for where to get the scripts. They are evil.
Their origins date back to the period when GDB was switching from K&R to
ISO C, and initially starting out on multiarch. They detected when
someone was slipping back into old K&R habits, but also made it possible
to track how many problematic things could reasonably be deleted.
The biggest wish list item is for it to compare the documentation
against the command set and report undocumented commands.
Andrew
prev parent reply other threads:[~2003-05-07 16:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 15:16 Kris Warkentin
2003-05-07 16:07 ` Andrew Cagney [this message]
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=3EB92F56.10209@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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).