diff options
| author | Keith Bostic <keith.bostic@mongodb.com> | 2016-06-17 12:00:59 -0400 |
|---|---|---|
| committer | Don Anderson <dda@mongodb.com> | 2016-06-17 12:00:59 -0400 |
| commit | a2a88dadb5a872010fa9930d54ebae810b8f780e (patch) | |
| tree | 482503f5e26ad65d479d134ac30c1181c2f3c381 /test/suite/test_cursor07.py | |
| parent | 36d657ccc67ce0fb5dd1881458ffc8a748b8aa44 (diff) | |
| download | mongo-a2a88dadb5a872010fa9930d54ebae810b8f780e.tar.gz | |
WT-2712 Coverity 1356928 and 1356929: ASSERT_SIDE_EFFECT (#2807)
Coverity complains:
CID 1356929: Incorrect expression (ASSERT_SIDE_EFFECT)
Assignment "tablename = strchr(opts->uri, 58)" has a side effect.
This code will work differently in a non-debug build.
90 testutil_assert((tablename = strchr(opts->uri, ':')) != 0);
I don't see it (there aren't any #ifdefs in the path to exit), my
suspicion is Coverity doesn't like side-effects in function calls
named with any variant of "assert".
Diffstat (limited to 'test/suite/test_cursor07.py')
0 files changed, 0 insertions, 0 deletions