Jump to content
  • Advertisement
Sign in to follow this  

Can't interpret crash message

This topic is 1244 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I was working on my Android project (thus connected to device), and was interrupted by a bizarre crash dump in eclipse-logcat, which i believe is not related to the program i was running. When i restarted, i ran (without modification) and continue my code successfully which confirms the crash dump was external.  I had inadvertently disconnected on previous occasions and crash message look different


 sad.png> WTF does that means?

.    < I don't know either,  except that i read on some lines.... "unknown source...".  


 I still need to know what it means in case its a security issue


Can anyone help interpret this:

[2015-07-23 06:58:24 - ddms] Can't bind to local 8600 for debugger
[2015-07-23 06:58:26 - ddmlib] An established connection was aborted by the software in your host machine
java.io.IOException: An established connection was aborted by the software in your host machine
	at sun.nio.ch.SocketDispatcher.write0(Native Method)
	at sun.nio.ch.SocketDispatcher.write(Unknown Source)
	at sun.nio.ch.IOUtil.writeFromNativeBuffer(Unknown Source)
	at sun.nio.ch.IOUtil.write(Unknown Source)
	at sun.nio.ch.SocketChannelImpl.write(Unknown Source)
	at com.android.ddmlib.JdwpPacket.writeAndConsume(JdwpPacket.java:213)
	at com.android.ddmlib.Client.sendAndConsume(Client.java:675)
	at com.android.ddmlib.HandleHeap.sendREAQ(HandleHeap.java:342)
	at com.android.ddmlib.Client.requestAllocationStatus(Client.java:521)
	at com.android.ddmlib.DeviceMonitor.createClient(DeviceMonitor.java:831)
	at com.android.ddmlib.DeviceMonitor.openClient(DeviceMonitor.java:799)
	at com.android.ddmlib.DeviceMonitor.deviceClientMonitorLoop(DeviceMonitor.java:617)
	at com.android.ddmlib.DeviceMonitor.access$100(DeviceMonitor.java:44)
	at com.android.ddmlib.DeviceMonitor$3.run(DeviceMonitor.java:576) 



Share this post

Link to post
Share on other sites

Sounds like firewall or some antivirus-like software on your pc prevented ddms from binding to port 8600.

Or perhaps there was other instance of ddms already running, so port 8600 was taken already.

Edited by vstrakh

Share this post

Link to post
Share on other sites
Sign in to follow this  

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!