View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004210 | unreal | ircd | public | 2013-05-21 12:06 | 2015-08-08 17:07 |
| Reporter | Assigned To | syzop | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | ||
| Target Version | 3.4-alpha1 | ||||
| Summary | 0004210: check for cleanliness with clang-analyzer and coverity | ||||
| Description | summary covers it all. i'd like to make a pass with coverity and clang-analyzer to ensure we're not doing anything too messed up. we've touched 100k lines of code since branching off 3.2 so :) | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
| child of | 0004215 | closed | Unreal 3.4 alpha2 blockers |
|
|
alpha1 goals for this done, pushing the remainder back to alpha2 as refactoring will sort the rest of the warnings. |
|
|
I know this isn't the same as a static code analyzer, but: I presume you guys also use valgrind when testing 3.4, right? Especially with so many code changes. |
|
|
I am using IBM's Purify as well as Valgrind. I committed a Valgrind suppressions file a while ago. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-05-21 12:06 |
|
New Issue | |
| 2013-05-21 12:06 |
|
Relationship added | child of 0004188 |
| 2013-05-25 01:31 |
|
Note Added: 0017670 | |
| 2013-05-25 01:32 |
|
Relationship deleted | child of 0004188 |
| 2013-05-25 01:32 |
|
Relationship added | child of 0004215 |
| 2013-05-25 15:51 | syzop | Note Added: 0017676 | |
| 2013-05-25 15:51 | syzop | Note Edited: 0017676 | |
| 2013-05-26 02:43 |
|
Note Added: 0017680 | |
| 2015-08-08 17:07 | syzop | Status | new => closed |
| 2015-08-08 17:07 | syzop | Assigned To | => syzop |
| 2015-08-08 17:07 | syzop | Resolution | open => no change required |
