From: Eli Zaretskii <eliz@gnu.org>
To: msnyder@sonic.net
Cc: gdb-patches@sourceware.org
Subject: Re: NEWS for 6.7: mention coverity bug fixes
Date: Sat, 18 Aug 2007 06:46:00 -0000 [thread overview]
Message-ID: <uabspuype.fsf@gnu.org> (raw)
In-Reply-To: <23843.12.7.175.2.1187384595.squirrel@webmail.sonic.net> (msnyder@sonic.net)
> Date: Fri, 17 Aug 2007 14:03:15 -0700 (PDT)
> From: msnyder@sonic.net
> Cc: msnyder@sonic.net, gdb-patches@sourceware.org
>
> >> Date: Fri, 17 Aug 2007 12:12:43 -0700 (PDT)
> >> From: msnyder@sonic.net
> >>
> >> Can we include this in 6.7 please?
> >
> > Yes, but...
> >
> >> + * 58 Coverity issues resolved in gdb, 29 in bfd, 1 in libiberty, and
> >> + 1 in opcodes. These include such things as resource leaks, null
> >> pointer
> >> + dereference, use after free, and array overruns.
> >
> > Are we sure the reader will know what is Coverity, and what does the
> > above mean to her/him?
>
> I'm open to suggestions. We could include their URL, for instance...
Yes, and a sentence about what it is.
Or maybe omit the name altogether, and just say that more than 80
issues with resource leaks etc. were resolved.
next prev parent reply other threads:[~2007-08-18 6:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 19:12 msnyder
2007-08-17 20:31 ` Eli Zaretskii
2007-08-17 21:03 ` msnyder
2007-08-18 6:46 ` Eli Zaretskii [this message]
2007-08-18 1:05 ` Nick Roberts
2007-08-18 5:08 ` Michael Snyder
2007-08-18 8:52 ` Nick Roberts
2007-08-18 15:39 ` Michael Snyder
2007-08-20 10:42 ` Nick Roberts
2007-08-20 11:29 ` Daniel Jacobowitz
2007-08-20 18:37 ` msnyder
2007-08-20 18:42 ` msnyder
2007-08-21 6:47 ` Nick Roberts
2007-08-20 19:11 ` Mark Kettenis
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=uabspuype.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@sonic.net \
/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