I'm trying to attach jdb to adb on a device, manually from a command line,
actually I'm writing an IDE extension that does it.
Whats going on is calling "adb shell am start -D ...", looking for a
debug port, port redirecting with "adb forward ..."
and then - attaching jdb.
Breakpoints for now are taken from ".jdbrc".
And what is happening is jdb stops doing anything after giving messages
about deferred breaks,
right before the messages that say the breaks are set, that appear
afterwards when all is going in a right way.
calling "adb kill-server" before seems to elliminate a problem, but I'm
not sure.
Is that problem well-known, or it's kind of my interaction with jdb
related bug?
By the way, does anybody know, is it possible not to start debugging
instantly after attaching to be able to set breaks manually and
not to use ".jdbrc".
System I'm on is Debian stable.
Thank you,
Alexander Petukhov
Hi,I'm trying to attach jdb to adb on a device, manually from a command line,
actually I'm writing an IDE extension that does it.Whats going on is calling "adb shell am start -D ...", looking for a
debug port, port redirecting with "adb forward ..."
and then - attaching jdb.
Breakpoints for now are taken from ".jdbrc".
And what is happening is jdb stops doing anything after giving messages
about deferred breaks,
Regards, Alexander