0xdeadd00d is a special address used by the dvmAbort() function to voluntarily crash the VM. Can you provide a stack trace ? that would give more information regarding the reason for this failure.
On Wed, Mar 11, 2009 at 8:28 PM, an...@android <[email protected]>wrote: > > hey guys, > i could able to build 'dalvikvm' on ppc . > i didnt build it for an emulator. > > I dont now how to test the 'dalvikvm' binary . > but when i ran the executable, i got an segmentation fault. > The log file of this can be found below. > > can anyone here help me out to test the 'dalvikvm' binary in ppc? > > > -------------------------------------------------------------------------------- > $ gdb dalvikvm > > GNU gdb Red Hat Linux (6.6-8.fc7rh) > Copyright (C) 2006 Free Software Foundation, Inc. > GDB is free software, covered by the GNU General Public License, and > you are > welcome to change it and/or distribute copies of it under certain > conditions. > Type "show copying" to see the conditions. > There is absolutely no warranty for GDB. Type "show warranty" for > details. > This GDB was configured as "ppc-redhat-linux-gnu"... > Using host libthread_db library "/lib/libthread_db.so.1". > (gdb) r > Starting program: /home/cupcake/out/debug/host/linux-ppc64/bin/ > dalvikvm > [Thread debugging using libthread_db enabled] > [New Thread -136015872 (LWP 780)] > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -136015872 (LWP 780)] > 0x0ff1a880 in dvmAbort () at dalvik/vm/Init.c:1433 > 1433 *((char*)0xdeadd00d) = 38; > (gdb) > > > ------------------------------------------------------------------------------------------------ > > Thanks in advance > Ananda > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
