Community
Participate
Working Groups
Created attachment 176091 [details] change to TestDwarfReader.java to not contain the variable "m" as one of the expected variables at location 0x10a2a (comments updated as well) context: the test of variables acquired by getScopedVariables() at 68138 (a.k.a. 0x102a2) had been relying on the end of the broken end-of-scope testing of https://bugs.eclipse.org/bugs/show_bug.cgi?id=322051 . when tested properly, "m" should not appear when the cursor is sitting on the final brace of the function. without https://bugs.eclipse.org/bugs/show_bug.cgi?id=322051, the tester probably saw the "m" when testing this, and incorrectly thought it was one of the variables to be counted when creating JUnitTest TestLocalScopes1. careful examination of the resource files being tested, together with independent testing of the executable built and run under edc, demonstrates that the variable should not appear at the point at which the JUnit test is doing its examination. attached fix: - change to TestDwarfReader.java to not contain the variable m as one of the expected variables at location 0x10a2a (comments updated as well)
Committed to HEAD.
*** cdt cvs genie on behalf of kryall *** Bug 322052 - edc JUnit test TestLocalScopes1 relying on incorrect visibility bug in one case [*] TestDwarfReader.java 1.11 http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.cdt/edc/org.eclipse.cdt.debug.edc.tests/src/org/eclipse/cdt/debug/edc/tests/TestDwarfReader.java?root=Tools_Project&r1=1.10&r2=1.11
