User forums > Using Code::Blocks

Using of arm-linux-androideabi-gdb

<< < (2/4) > >>

oBFusCATed:
You've not set any breakpoints, so your app should just run to completion.
What are you expecting to happen?

The program's arguments should be ignored when remote debugging...

SteelRat:
I tried to set breakpoints before by C::B. Then i cleared them. And i think that one of them was stored in gdbserver's cache, can it be? I expect that C::B debugs android's app as usual executable. But now works only "continue".

oBFusCATed:
I don't think there is any gdbserver cache.

After you press debug does your app runs normally on your android?

SteelRat:
My actions:
1. I'm starting shell script that kills app on Android and starts it.
 a. Receiving PID of app's process.
 b. Starting gdbserver on android, attaching it to received PID.
2. Starting remote debugging in C::B. To this moment app's is already in paused state. When i did first times - there was no pause. It appears when i tried to set breakpoints in C::B and then i remoed all breakpoints.   :-\

As you see it take pretty much of time, when breakpoint in "main" is missed already.
I'm planning to set eternal loop in the very begining. Something like this:

--- Code: ---int i = 0;
while (i == 0)
{
};

--- End code ---
Then i'll write in "Additional GDB commands->After connection" set var i = 1.

oBFusCATed:
Hm, why are you using localhost as host?
Are you using some kind of emulator?
Have you tried to use gdb directly to see if the problem is cause by C::B or gdb?

Navigation

[0] Message Index

[#] Next page

[*] Previous page