From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Coverity Scan on Newlib
Date: Wed, 15 Mar 2017 14:32:00 -0000 [thread overview]
Message-ID: <174fdeb0-983c-e00d-5c68-988b1f5ff87d@oarcorp.com> (raw)
Hi
I setup Newlib targeting RTEMS as a Coverity Scan
project. Corinna has mentioned having one under
Cygwin but the variation of not being built
for Cygwin tripped at least one issue that would
show up on all non-Cygwin targets.
For the most part, this shouldn't be particularly
different from any other non-Cygwin build of
newlib.
The project and output are here:
https://scan.coverity.com/projects/rtems-newlib
It is built by the script do_coverity_newlib in
https://git.rtems.org/rtems-testing/tree/coverity.
Obviously you need an RTEMS toolset for that
configuration.
There are 66 issues reported in yesterday's run.
I am really hoping the newlib community can pitch
in to triage and resolve these.
Thanks.
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35806
Support Available (256) 722-9985
reply other threads:[~2017-03-15 14:32 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=174fdeb0-983c-e00d-5c68-988b1f5ff87d@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=newlib@sourceware.org \
/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).