On Jul 31, 9:18 am, zhtlancer wrote:
> When I tried to build the InterpC-allstubs.c, the compile complaint
> like this:
> dalvik/vm/mterp/out/InterpC-allstubs.c: In function
> ‘dvmMterp_OP_GOTO’:
What type of build are you configured for?
Have you made any local modifications?
--~--~-~
Thanks for your reply, I'am trying to port dalvik to a new platform
I've just found out why this happened, and I think this may be a bug.
In dalvik/vm/mterp/cstubs/stubdefs.c, there is a "#define self glue->self"
But in line 115, wrote "glue->self->threadId", so I changed it to
"self->threadId",
On Jul 31, 10:16 am, zhtlancer wrote:
> I've just found out why this happened, and I think this may be a bug.
> In dalvik/vm/mterp/cstubs/stubdefs.c, there is a "#define self glue->self"
> But in line 115, wrote "glue->self->threadId", so I changed it to
> "self->threadId", and re-generate Inter
thanks for your help.
I've another problem here.
How can I examine the log information of dalvik on a non-Android system?
I've checked that dalvik writes its log into /dev/log/main, but there is no
that device file on my system.
So I just placed a empty text file in that place for dalvik to write
On Jul 31, 8:13 pm, zhtlancer wrote:
> How can I examine the log information of dalvik on a non-Android system?
> I've checked that dalvik writes its log into /dev/log/main, but there is no
> that device file on my system.
> So I just placed a empty text file in that place for dalvik to write log
thanks for your reply
On Tue, Aug 4, 2009 at 1:27 AM, fadden wrote:
>
> On Jul 31, 8:13 pm, zhtlancer wrote:
> > How can I examine the log information of dalvik on a non-Android system?
> > I've checked that dalvik writes its log into /dev/log/main, but there is
> no
> > that device file on my
