Hi fadden,
Thank you for your answer.
I have tried to free allocated heap memory to avoid leak memory.
I'm meeting another issue about libffi issue and would like to have
your comment about it.
When Dalvik VM calls to libffi, it causese Dalvik crash with below
stack trace:
stack trace information:
SP:0x8614c790(unknown stack base:0x8fa00000)
0x80ca83cc:JNI_GetCreatedJavaVMs + 0x6d4
0x80c52220:Java_vnc_impl_http_ServerRequest_rawFrameBufferUpdate +
0x208 -> JNI_GetCreatedJavaVMs()
0x80c50ce4:ffi_call_N32 + 0x4fc ->
Java_vnc_impl_http_ServerRequest_rawFrameBufferUpdate()
Would you advise me what is problem with my porting libffi issue?
How to make sure whether my porting lbffi on MIPS works correctly or
not?
Thanks so much,
Best regards
On Jul 28, 2:18 am, fadden <[email protected]> wrote:
> On Jul 27, 4:49 am, Mercury <[email protected]> wrote:
>
> > Could you please advice me why I call free as the above implement
> > cause crash?
>
> I don't know.
>
> > If possible, could you tell me or share me a document about the design
> > of heap implement in Dalvik?
>
> There isn't one. It uses the dlmalloc "mspace" stuff to manage the
> storage, and has some additional structures (e.g. the object "mark"
> bitmap) on top. You can find some documentation about dlmalloc on the
> web (e.g.http://g.oswego.edu/dl/html/malloc.html).
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---
