how to debug engine layer crash without stack information?

by kevin ma » Wed, 22 Jul 2009 05:48:50 GMT

Sponsored Links
 Dear all,
    I'm debugging opencore related app & engine. Normally, when met
engine layer crash issue, we will get the stack info printed in the
log as below.

I/DEBUG   (   33):          #00  pc 00111dac  /system/lib/
I/DEBUG   (   33):          #01  pc 00112c66  /system/lib/
I/DEBUG   (   33):          #02  pc 00105ff0  /system/lib/
I/DEBUG   (   33):          #03  pc 00082b98  /system/lib/
I/DEBUG   (   33):          #04  pc 00042fe2  /system/lib/
I/DEBUG   (   33):          #05  pc 0004346c  /system/lib/
I/DEBUG   (   33):          #06  pc 00043088  /system/lib/
I/DEBUG   (   33):          #07  pc 00040e18  /system/lib/
I/DEBUG   (   33):          #08  pc 000ede86  /system/lib/
I/DEBUG   (   33):          #09  pc 000edf48  /system/lib/
I/DEBUG   (   33):          #10  pc 000f56b6  /system/lib/
I/DEBUG   (   33):          #11  pc 000f50f4  /system/lib/
I/DEBUG   (   33):          #12  pc 00032a50  /system/lib/
I/DEBUG   (   33):          #13  pc 00032c7c  /system/lib/
I/DEBUG   (   33):          #14  pc 00032e44  /system/lib/
I/DEBUG   (   33):          #15  pc 001109ec  /system/lib/
I/DEBUG   (   33):          #16  pc 00110b40  /system/lib/
I/DEBUG   (   33):          #17  pc 0002affe  /system/lib/
I/DEBUG   (   33):          #18  pc 000285d4  /system/lib/
I/DEBUG   (   33):          #19  pc 0000f8cc  /system/lib/
I/DEBUG   (   33):          #20  pc 0000f438  /system/lib/

    But sometimes, we can not get these info. So it's very hard to fix
the bug at that time. Does anyone know some method to solve this
problem? Thanks!

Best Regards,

how to debug engine layer crash without stack information?

by fadden » Wed, 22 Jul 2009 18:23:39 GMT


I posted some information about transforming stack traces here:


Sponsored Links

how to debug engine layer crash without stack information?

by kevin ma » Thu, 23 Jul 2009 01:22:49 GMT

 Dear fadden,
    Thanks for your great help! The key issue is when my app crash, I can
not get the stack information now. I just wondering when will the stack info
generated and print out, when it will not, when crash met. Thanks!

Best Regards,

2009/7/23 fadden <>


how to debug engine layer crash without stack information?

by fadden » Thu, 23 Jul 2009 19:24:09 GMT


Some info here:

Other Threads

1. Blue Screen of Death when debugging againstactual phone

I'm not sure what's causing anyone so many issues. The way I load apps to it 
seems pretty simple I just plug the g1 in and close the emulator if open and 
then run the program it auto chooses the device as the emulator no command line 
-----Original Message-----

Date: Fri, 31 Oct 2008 17:54:38 
To: Android Developers<>
Subject: [android-developers] Blue Screen of Death when debugging against
 actual phone

I've installed the Windows USB driver for the G1 to be able to debug
applications.  When I plug the phone in via USB I can see it listed
via 'adb devices'.  In Eclipse when I run the app it pops up to select
the device (Emulator or G1).  I pick the phone and immediately the
system blue screens and then reboots.  The reboot is quick and
automatic so I can't see much on the blue screen other than something
about BUGCODE_USB_....
I've tried this 4 or 5 times with the same result every time.

This is on Windows XP Pro service pack 3 with Eclipse Ganymede.

Anyone have any ideas?


2. RSS Normalizing Crashes App

I'm writing a script that takes a RSS and phrases items.. but it is
crashing on part of the code.

I'm using the code from:

private void DownloadRSS(String URL)
        InputStream in = null;
        try {
            in = OpenHttpConnection(URL);
            Document doc = null;
            DocumentBuilderFactory dbf =
            DocumentBuilder db;

            try {
                db = dbf.newDocumentBuilder();
                doc = db.parse(in);
            } catch (ParserConfigurationException e) {
                // TODO Auto-generated catch block
            } catch (SAXException e) {
                // TODO Auto-generated catch block


            //---retrieve all the <item> nodes---
            NodeList itemNodes = doc.getElementsByTagName("item");

            String strTitle = "";
            for (int i = 0; i < itemNodes.getLength(); i++) {
                Node itemNode = itemNodes.item(i);
                if (itemNode.getNodeType() == Node.ELEMENT_NODE)
                    //---convert the Node into an Element---
                    Element itemElement = (Element) itemNode;

                    //---get all the <title> element under the <item>
                    // element---
                    NodeList titleNodes =

                    //---convert a Node into an Element---
                    Element titleElement = (Element) titleNodes.item

                    //---get all the child nodes under the <title>
                    NodeList textNodes =
                        ((Node) titleElement).getChildNodes();

                    //---retrieve the text of the <title> element---
                    strTitle = ((Node) textNodes.item(0)).getNodeValue

                    //---display the title---
        } catch (IOException e1) {
            // TODO Auto-generated catch block

It is crashing the app when it gets to: doc.getDocumentElement

(And it won't work without it.. Some work.. some RSS files do not.)

Is this the best way to do it? I want to load the fields "title" and
"link" into an array.. and then list them and make it clickable.


3. Serialization of WebView Object

4. Permission READ_LOGS

5. Android & IPC

6. shopsavvy violates shop guideline

7. Cross platform app payments system