From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>
Cc: Matthew Fioravante <matthew.fioravante@jhuapl.edu>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ian Campbell <Ian.Campbell@citrix.com>,
Rob Hoes <rob.hoes@citrix.com>
Subject: New Coverity issues (tools/libxl/testidl.c)
Date: Wed, 4 Dec 2013 17:28:26 +0000 [thread overview]
Message-ID: <529F663A.4030604@citrix.com> (raw)
>From the latest run, there have been two new issues. They are both in
testidl.c, which appears to be code generated by gentests.py
CID1135378: in libxl_domain_build_info_rand_init()
CID 1135379: in libxl_event_rand_init()
In both cases, the complain is that in each function is a
"switch(p->type)" where p->type is completely uninitialised.
The complain looks genuine, but I defer to people more familiar with the
IDL and gentests.py for suggestions of how to fix it.
~Andrew
next reply other threads:[~2013-12-04 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 17:28 Andrew Cooper [this message]
2013-12-04 17:48 ` [PATCH] tools: libxl: testidl: initialise the KeyedUnion keyvar before the union Ian Campbell
2013-12-04 17:54 ` Andrew Cooper
2013-12-05 11:39 ` Ian Campbell
2013-12-10 14:12 ` Ian Jackson
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=529F663A.4030604@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=matthew.fioravante@jhuapl.edu \
--cc=rob.hoes@citrix.com \
--cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.