mxnet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kellen sunderland <>
Subject Re: Coverity scan
Date Fri, 02 Nov 2018 16:07:58 GMT
Hey Anton, can you provide a sample scan?  I'm interested to see if it
catches different memory access violations, or if it gets the same ones
we've already seen reported by clang-tidy.  For example are these
violations in the reports:
warning: Access to field 'capacity' results in a dereference of a null
pointer (loaded from variable 'mainHash')


/work/mxnet/3rdparty/mshadow/mshadow/./tensor.h:64:23: warning:
Assigned value is garbage or undefined
      this->shape_[i] = s[i];"


warning: Use of memory after it is freed



On Fri, Nov 2, 2018 at 2:20 AM Anton Chernov <> wrote:

> Dear MXNet community,
> I had investigated the possibility to adopt Coverity static analysis tools
> for the MXNet project and it turned out that there is a tool provided by
> Synopsys for open-source projects:
> The tool works nicely with GitHub [1] and I found that a scan for a fork
> (from @apeforest) [2] was already set up. I can not tell how long ago the
> scan was performed, but at the time of writing the project page shows 5
> illegal memory access errors, that I think would be worth investigating.
> If there is interest I would suggest that we would setup a Coverity scan
> for the main repository instead of a fork and people that have interest
> managing and fixing issues would request add them to the project.
> I would appreciate feedback for this proposal and help from people having
> rights for the main repository to set things up.
> Best regards,
> Anton
> [1]
> [2]

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message