Issue 162 in toped: cppcheck give some errors

2 views
Skip to first unread message

to...@googlecode.com

unread,
Feb 6, 2013, 10:52:14 PM2/6/13
to toped...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 162 by xian...@openmobilefree.net: cppcheck give some errors
http://code.google.com/p/toped/issues/detail?id=162

svn version r2361:

$ ~/toped-read-only$ cppcheck -j8 --quiet -f .
[src/toped.cpp:1386]: (error) Uninitialized variable: success
[src/tui.cpp:1403]: (error) Memory leak: newpat
[tpd_DB/tedesign.cpp:1765]: (error) Uninitialized variable: shapes
[tpd_GL/trend.cpp:732]: (error) Mismatching allocation and deallocation:
infoLog
[tpd_GL/trend.cpp:749]: (error) Mismatching allocation and deallocation:
infoLog

to...@googlecode.com

unread,
Feb 10, 2013, 8:41:12 AM2/10/13
to toped...@googlegroups.com
Updates:
Status: Fixed
Labels: OpSys-All Component-Other Maintainability

Comment #1 on issue 162 by krustev....@gmail.com: cppcheck give some errors
http://code.google.com/p/toped/issues/detail?id=162

Fixed in r2362. All apart from
[src/tui.cpp:1403]: (error) Memory leak: newpat
The variables above are cleaned-up in the destructor of that class. The
report doesn't look to be correct.

to...@googlecode.com

unread,
Feb 10, 2013, 9:08:56 AM2/10/13
to toped...@googlegroups.com
Updates:
Owner: krustev....@gmail.com

Comment #2 on issue 162 by krustev....@gmail.com: cppcheck give some errors
http://code.google.com/p/toped/issues/detail?id=162

(No comment was entered for this change.)

to...@googlecode.com

unread,
Apr 4, 2013, 6:39:51 PM4/4/13
to toped...@googlegroups.com
Updates:
Status: Verified

Comment #3 on issue 162 by krustev....@gmail.com: cppcheck give some errors
http://code.google.com/p/toped/issues/detail?id=162

(No comment was entered for this change.)

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
Reply all
Reply to author
Forward
0 new messages