Java Result: -1073740791

[PreethiGowri]

Well, yes i have used printstacktrace s and printlines. The code exactly terminates when i try to send the data, after packetizing it. This is the code line

 sender.sendPacket(sendPacket);

where sendPacket is the byte array that holds the data packet.

[r035198x]

Did you wrap just the sendPacket call in a try/catch then?
What does the documentation of the sendPacket method say? Did you write it or is it part of some third party A.P.I

[PreethiGowri]

yes, i did wrap the code line within a try catch block, Its a part of third party API of this " UDPPacket sendPacket = new UDPPacket(55000 , 61000);"

here is the code snippet of what and how i'm doing,

try {
                InetAddress src = null;
                InetAddress dest = null;
                if (pack instanceof IPPacket) {
                    IPPacket ipp = (IPPacket) pack;
                    src = ipp.dst_ip;
                    dest = ipp.src_ip;
                }
                EthernetPacket etherSrc = ((EthernetPacket) pack.datalink);
                byte[] gwmac = null;
                gwmac = etherSrc.src_mac;
                System.out.println("dest mac : " + gwmac);
                JpcapSender sender = JpcapSender.openDevice(devices[index]);
                UDPPacket sendPacket = new UDPPacket(55000, 61000);

                sendPacket.setIPv4Parameter(0, false,                             
                    false, false, 0, false,
         false, false, 0, 1010101, 100,
         IPPacket.IPPROTO_UDP,
                        src, dest);
                String outData = DAO.getBay(bay);
                sendPacket.data = outData.getBytes();
                EthernetPacket ether = new     EthernetPacket();
                ether.frametype = EthernetPacket.ETHERTYPE_IP;
                ether.src_mac = devices[index].mac_address;
                ether.dst_mac = gwmac;
                sendPacket.datalink = ether;
                System.out.println("back to sendbay");
                
                try{
                sender.sendPacket(sendPacket);
                }
               catch ( RuntimeException ex) {
                ex.printStackTrace(System.out);
                Logger.getLogger(New.class.getName()).log(Level.SEVERE, null, ex);
            }  
            }
            catch (IOException ex) {
                Logger.getLogger(New.class.getName()).log(Level.SEVERE, null, ex);
            }

[r035198x]

Don't do

catch ( RuntimeException ex) {
                ex.printStackTrace(System.out);
                Logger.getLogger(New.class.getName()).log(Level.SEVERE, null, ex);
            }

Then check the APIs for those external classes as well to make sure you're calling them with right values.

Just do

catch ( Exception ex) {
                ex.printStackTrace();

            }

[PreethiGowri]

2 windows pop up asking,

window 1:
Java(TM) platform SE binary has stopped working
Windows is collecting more information about the problem. This might take several minutes...

Window 2:
Do you want to send more information about the problem?
Additional details about what went wrong can help Microsoft create a solution.

[kuat]

The solution for me was here:

http://stackoverflow.com/questions/14599504/how-to-increase-the-heap-size-while-using-the-new-eclipse-adt-environment

From what I understand, the problem is occurring because your max heap size is being exceeded during some processing event - be it in the development kit or while emulating. The good thing is that you can alter the max heap size in the android.ini file (it's at the very end.) I changed mine to 1024M.