It does not give me a trace at all. The dalvik only reports a process exit by sig 11.
On Tue, Jul 7, 2009 at 11:06 AM, Chen Yang <sunsety...@gmail.com> wrote: > Fadden: > Thanks. > I don't have it at present. > Is there some good approach for generating the native stack trace? It seems > in my case, it just aborts and restarts the zygote again and again. > > From what I have observed, it dumped some weird value as reference, the > value doesn't belong to any dalvik heap. > one case I remembered: > IS_CLASS_FLAG_SET(clazz, CLASS_ISARRAY) in scanObject: caused segfault > > Any plan to introduce the precise GC soon? Thanks. > -- > Chen > > On Wed, Jul 8, 2009 at 1:49 AM, fadden <fad...@android.com> wrote: > >> >> On Jul 7, 10:41 am, Chen Yang <sunsety...@gmail.com> wrote: >> > just curious to know: is the arm version working correctly? >> > From what i have observed on x86, the introduced code by that patch >> brought >> > none reference stuff as reference, which caused the runtime segmentation >> > fault. >> >> We don't see a segmentation fault here, though it does fail to start >> up on the ARM emulator (some keystore problem). >> >> Do you have a native stack trace from the core dump? >> >> >> --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
