Eclipse Debugger does not advance in Android application

Question

Eclipse Debugger does not advance in Android application

Navigation

#1 by (1 votes)
#2 by (0 votes)

2

I'm having a problem trying to debug an Android application in Eclipse. When I press the F5, F6 or F8 keys, simply the break point line does not pass to the next instruction (line), it stops. I had already used the Eclipse Debug and had never had problems.

Look at the screenshot of my Eclipse and the code I'm trying to debug. I have tried to summarize, but still the break point does not advance to the next line.

voidinit(){txtFrequencia=(EditText)findViewById(R.id.editText_Frequencia);txtQuantidade=(EditText)findViewById(R.id.editText_Quantidade);txtIntervalo=(EditText)findViewById(R.id.editText_Intervalo);txtNomeMedicamento=(EditText)findViewById(R.id.editText_NomeMedicamento);tmpInicioTratamento=(TimePicker)findViewById(R.id.timePicker_InicioTratamento);spnTipoDosagem=(Spinner)findViewById(R.id.spinner_TipoDosagem);btnSalvar=(Button)findViewById(R.id.button_salvar_agenda);toast=Toast.makeText(this.getApplicationContext(),"Você Apertou o Botão", Toast.LENGTH_SHORT);
    btnSalvar.setOnClickListener(new View.OnClickListener() {

        public void onClick(View v) {

            add();

        }
    });
}

Note: I have already tested in two versions of Eclipse and I am using Windows 8 64bit

android eclipse debug

asked by anonymous 13.02.2014 / 21:06

2 answers

How to convert a JSON object to XML in AS3? Login with Java levels MySQL

score 1 · Answer 1

In my opinion you should be experiencing the problem of mapping shortcut keys in eclipse. My suggestion is that you reset to the original settings. in:

Window > Preference > General > Keys

Select the Scheme Default and then click the "Restore Defaults" button.

If the problem still occurs check that you can follow the next steps through the shortcut in the menu.

score 0 · Answer 2

Sometimes I have had this problem, it can be two things:

The Eclipse window is out of focus. Clicking on it returns the commands;

The Thread selected from the Debug perspective is not the same Thread that is suspended. In this case, I had to find in the list the Thread that appears with a yellow pause icon, click on it to have the commands working back.