Android Question Debugger: java.lang.RuntimeException: java.net.SocketException: Socket closed

Rusty

Well-Known Member
Licensed User
Longtime User
I saw your previous post on this error and note the response therein. However, this makes it where I can't use the debugger to debug my code.
When I compile in Debug mode, it get the following:

The exact (unchanged) code compiled release (obfuscated) works perfectly, but the debug version dies and the running compiled code completely stops.
Any suggestions on how I can compile and use b4abridge (v2.14, ...newer version available?) in debug mode?
Thanks,
Rusty
 

Rusty

Well-Known Member
Licensed User
Longtime User
It seems to happen with the "main" application. The subordinate/supporting apps are all very small and don't seem to have this problem.
I also still have the problem (which may be related) that the debugger does not break on breakpoints unless I set/unset/set/unset... breakpoints or make a series of consecutive breakpoints around the point at which I wish to actually break.
For example:

USUALLY won't break, but:

Will USUALLY break, and it might not even break until you hit line (for example) 5077 or 5088.
It also helps if you set/reset...etc. continually while the program is installing (after compile) to b4aBridge or via USB. It is very unreliable to obtain a debug break.

I mention this because someone in a previous post mentioned that when one gets the error (in the post title), if they remove breakpoints it will work. I tried deleting all the breakpoints and the (title) error goes away...

BTW, the "main" app is very large, 13000+ lines in MAIN with about 100 services, classes and modules adding up to 1000's of line of more code. Don't know if this matters or not.
And finally, this is an app to which the Starter service can NOT be added.
Regards,
Rusty
 
Upvote 0
Cookies are required to use this site. You must accept them to continue using the site. Learn more…