Bugzilla – Full Text Bug Listing
| Summary: | Possible free on undefined variable | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Niels Thykier <niels> |
| Component: | Resources | Assignee: | Platform-Resources-Inbox <platform-resources-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.1 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |
Build Identifier: Hey cppcheck (1.44) reveals that the native code may be calling free() on an undefined variable in natives/win32/localfile.c (two times): [natives/win32/localfile.c:562]: (error) Uninitialized variable: targetFile [natives/win32/localfile.c:614]: (error) Uninitialized variable: targetFile I have verified these and it happens in this condition (in both cases): if (mid == 0) goto fail; ~Niels Reproducible: Always