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/
libopencore2way.so
I/DEBUG   (   33):          #01  pc 00112c66  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #02  pc 00105ff0  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #03  pc 00082b98  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #04  pc 00042fe2  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #05  pc 0004346c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #06  pc 00043088  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #07  pc 00040e18  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #08  pc 000ede86  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #09  pc 000edf48  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #10  pc 000f56b6  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #11  pc 000f50f4  /system/lib/
libopencoreauthor.so
I/DEBUG   (   33):          #12  pc 00032a50  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #13  pc 00032c7c  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #14  pc 00032e44  /system/lib/
libopencorecommon.so
I/DEBUG   (   33):          #15  pc 001109ec  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #16  pc 00110b40  /system/lib/
libopencore2way.so
I/DEBUG   (   33):          #17  pc 0002affe  /system/lib/
libandroid_runtime.so
I/DEBUG   (   33):          #18  pc 000285d4  /system/lib/libutils.so
I/DEBUG   (   33):          #19  pc 0000f8cc  /system/lib/libc.so
I/DEBUG   (   33):          #20  pc 0000f438  /system/lib/libc.so




    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,
Kevin
--~--~---------~--~----~------------~-------~--~----~



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,
Kevin

2009/7/23 fadden <fad...@android.com>


> 



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. ALSA channels

when i use the code below.
status_t ALSAStreamOps::channelCount(int channels) {
    int err;
    if (!mHandle)
        return NO_INIT;
    err = snd_pcm_hw_params_set_channels(mHandle, mHardwareParams,
channels);
    if (err < 0) {
        LOGE("Unable to set channel count to %i: %s",
            channels, snd_strerror(err));
        return BAD_VALUE;
    }
    LOGD("Using %i %s for %s.",
        channels, channels == 1 ? "channel" : "channels", streamName());
    return NO_ERROR;
}

i want to set channel 1 when recoring audio. but the message of "Unable to
set channel count to %i: %s" will be print .who know why?

--~--~---------~--~----~------------~-------~--~----~

2. Eclipse Error: SWT on ubuntu (amd turion )64 bit

Hi
i've just tried to install SDK 1.5 and I have a big problem,
when I try to point the sdk directory(in Eclipse 3.3.2) from "Windows-
"...pingUsageServerfailed" in the second "An SWT erro has occured.We
are reccomended to exit the workbench. .....".
Now I've ridden some blogs and I've understood that the problem is in
SWT that doesn't support 64bit
architecture.
What shall I do?
Please answer in a simple.
Lorenz

--~--~---------~--~----~------------~-------~--~----~

3. PingUsage Server failed

4. Questions on Tab (TabWidget) Width

5. Get Latitude/Longitude informations of an image

6. Hello World Tutorial Error Message

7. Handling key events in a paused Activity