eclipse - Where can a stale binary hide when developing an android app? -
eclipse - Where can a stale binary hide when developing an android app? -
guess found myself: apparently else-if block detected unreachable code , not compiled binary. @ to the lowest degree conclusion now. it's 7am. farther investigate after little nap.
i'm totally lost , lost day on digging deep.
i have android app. @ point, changes not debugged anymore. seamed running stale code. i've done obvious (refresh, project clean), less obvious (eclipse -clean, fresh checkout of project) , lastly thing did was:
download eclipse install mercurial , adt install android sdk checkout project virgin workspace run app in newly created virtual deviceguess what, still behaves follows:
when set breakpoint @ "// breakpoint" pressing f6 (step over) can step through "// 1" , "// 2" although after //1, //2 should unreachable. debugger knows nil variables in else-if block while i'm @ //1
} else if (column == 4) { // breakpoint textview cardsetlabel = (textview) view; string name = cursor.getstring(cardsetcolumnindex); name = name.substring(0, math.min(15, name.length() - 1)); cardsetlabel.settext(name); // 1 homecoming true; } homecoming false; // 2
actually if delete whole surrounding code block, stuff still remains intact. voodoo, sorry. @ to the lowest degree deleting whole activity results in activity beingness gone @ run time, theory of stuff beingness stale not option.
please, help appreciated :(
is possible you're hitting //1 on 1 iteration , //2 on another? maybe enclosing method called twice consecutively.
maybe seek uninstalling/installing adb, typing paths in manually sure things pointing think are. check manually build directory clean in between clean , fresh build.
add log message in there, , watch in logcat sure you're running fresh code.
android eclipse
Comments
Post a Comment