VFY: unable to find class referenced in signature

by hefeng » Tue, 07 Jul 2009 00:06:43 GMT


Sponsored Links
 Hello,

I try to port the XMPP library to android sdk 1.5, follow the demo
ApiDemo from the sdk,  I created a directory something like below:

      smack--+AndroidManifest.xml                          ..The
manifest for the smack library

                    |
 
+src                                                     ..The source
code for the smack
                    :
                    :
                    ------
test                                              .. The test
directory for the test case
                                  |
                                 +
AndroidManifest.xml                              .. The manifest for
the test code
                                  |
                                  :
                                  :
 
+src                                                            .. The
test code for the smack library.

After I build both projects, I install them respectively on the
emulator, then I launch the test case by command:
$ adb shell am instrument -w org.jivesoftware.smack.test/
android.test.InstrumentationTestRunner

then console output following information:
$INSTRUMENTATION_RESULT: shortMsg=org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_RESULT: longMsg=java.lang.VerifyError:
org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_CODE: 0

I think there is something wrong with the test case then I check with
command:

$adb logcat

I found following error message in the log:
:
:
D/AndroidRuntime( 1216): --- registering native functions ---
D/ActivityManager(  564): Uninstalling process
org.jivesoftware.smack.test
I/ActivityManager(  564): Start proc org.jivesoftware.smack.test for
added application org.jivesoftware.smack.test: pid=1223 uid=10019 gids=
{}
W/dalvikvm( 1223): VFY: unable to find class referenced in signature
(Lorg/jivesoftware/smack/XMPPConnection;)
E/dalvikvm( 1223): Could not find method
org.jivesoftware.smack.XMPPConnection.connect, referenced from method
org.jivesoftware.smack.LoginTest.testInvalidLogin
W/dalvikvm( 1223): VFY: unable to resolve virtual method 176: Lorg/
jivesoftware/smack/XMPPConnection;.connect ()V
:
It seems there is something wrong for the dalvik to resolve the
connect method in the org.jivesoftware.smack package, so I type the
command

$ adb shell dexdump -d -f -h /data/dalvik-cache/
d...@app@org.jivesoftware.smack....@classes.dex | grep XMPPConnection

then, I find following information in output
    #4              : (in Lorg/jivesoftware/smack/XMPPConnection;)
013130:                                        |[013130]
org.jivesoftware.smack.XMPPConnection.connect:()V

It seems that the XMPPConnection class with its method have been
install properly already.



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



VFY: unable to find class referenced in signature

by hefeng » Tue, 07 Jul 2009 00:07:21 GMT


 Hello,

I try to port the XMPP library to android sdk 1.5, follow the demo
ApiDemo from the sdk,  I created a directory structure something like
below for two packages org.jivesoftware.smack &
org.jivesoftware.smack.test :

      smack--+AndroidManifest.xml               ..The manifest for
package org.jivesoftware.smack

                    |
 
+src                                                 ..The source code
for the smack
                    :
                    :
                    ------
test                                          .. The test directory
for the test case
                                  |
                                 + AndroidManifest.xml              ..
The manifest for the package   org.jivesoftware.smack.test
                                  |
                                  :
                                  :
 
+src                                                            .. The
test code for the smack library.

After I build both projects, I install both package respectively on
the emulator, then I try to launch the test case by command:
$ adb shell am instrument -w org.jivesoftware.smack.test/
android.test.InstrumentationTestRunner

then console output following information:
$INSTRUMENTATION_RESULT: shortMsg=org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_RESULT: longMsg=java.lang.VerifyError:
org.jivesoftware.smack.LoginTest
$INSTRUMENTATION_CODE: 0

I think there is something wrong with the test case then I check with
command:

$adb logcat

I found following error message in the log:
:
:
D/AndroidRuntime( 1216): --- registering native functions ---
D/ActivityManager(  564): Uninstalling process
org.jivesoftware.smack.test
I/ActivityManager(  564): Start proc org.jivesoftware.smack.test for
added application org.jivesoftware.smack.test: pid=1223 uid=10019 gids=
{}
W/dalvikvm( 1223): VFY: unable to find class referenced in signature
(Lorg/jivesoftware/smack/XMPPConnection;)
E/dalvikvm( 1223): Could not find method
org.jivesoftware.smack.XMPPConnection.connect, referenced from method
org.jivesoftware.smack.LoginTest.testInvalidLogin
W/dalvikvm( 1223): VFY: unable to resolve virtual method 176: Lorg/
jivesoftware/smack/XMPPConnection;.connect ()V
:
It seems there is something wrong for the dalvik to resolve the
connect method in the org.jivesoftware.smack package, so I type the
command

$ adb shell dexdump -d -f -h /data/dalvik-cache/
d...@app@org.jivesoftware.smack....@classes.dex | grep XMPPConnection

then, I find following information in output
    #4              : (in Lorg/jivesoftware/smack/XMPPConnection;)
013130:                                        |[013130]
org.jivesoftware.smack.XMPPConnection.connect:()V

It seems that the XMPPConnection class with its method have been
install properly already, then I lost ideal how to finger out the
problem, please give me a hand, any comments are appreciated.

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


Sponsored Links


VFY: unable to find class referenced in signature

by fadden » Tue, 07 Jul 2009 03:41:15 GMT


 


I'd guess that the org.jivesoftware.smack.apk file is not present in
the process responding to the instrumentation test request.

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



Other Threads

1. How to get Android working on the eeepc?

Hi,

I've had a fair share of problems building a 2.6.27 Kernel for the
eeepc.

Most of them regard the building of the framebuffer. Stock 2.6.27
i915.ko doesn't support the modeset parameter.

i915 development has been phased out of freedesktop.org and moved into
the kernel, so I can't find the sources for a recent module (except in
any recent Linux kernels).

Does anyone have any hints on compiling the framebuffer/drm module or
getting it to work?

A nudge in the right direction would be sufficient. :)

Kind regards,

Falk

--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

2. in case of building adb composite gadget dynamicall

Hi~ there,

I've been trying to build "g_android"(ADB Composite Gadget)
dynamically.

In case of building statically, ADB and Mass-storage are working well.

But dynamical building doesn't work, I have no idea how to solve this
problem.

My init.rc add g_android.ko using "insmod /lib/modules/g_android.ko".

When I connect the usb cable into a Windows PC,
the target device meets Kernel Panic as the bottom of this e-mail.

My CPU is S3C6410, it runs under linux kernel 2.6.27

Can any one give some help?

Hoping that each day will you feel better

Thanks in advance.

Best Regards,


//Message of Kernel panic
Unable to handle kernel paging request at virtual address e1a02001
pgd = c84c4000
[e1a02001] *pgd=00000000
Internal error: Oops: 1 [#1]
Modules linked in: compass acc_sensor s3c_camera s3c_cmm s3c_g3d
s3c_jpeg s3c_pp
 s3c_g2d_driver s3c_mfc s3c_rotator {*filter*} multipdp yaffs2 dpram
g_android
CPU: 0    Not tainted  (2.6.27 #30)
PC is at composite_setup+0x120/0xa80 [g_android]
LR is at 0x3
pc : [<bf003a8c>]    lr : [<00000003>]    psr: 60000193
sp : c801dd30  ip : e1a02001  fp : c801dd7c
r10: 00080000  r9 : 40000113  r8 : 00000000
r7 : c05c4ccc  r6 : c8565fa0  r5 : 00000000  r4 : 00000100
r3 : e1a01fe1  r2 : e1a01fe1  r1 : c8565fc4  r0 : 00000000
Flags: nZCv  IRQs off  FIQs on  Mode SVC_32  ISA ARM  Segment user
Control: 00c5387f  Table: 584c4008  DAC: 00000015
Process init (pid: 1, stack limit = 0xc801c260)
Stack: (0xc801dd30 to 0xc801e000)
dd20:                                     c801dd4c c05c4ccc f7900000
c052e4c0
dd40: c8565f20 00000040 40000113 00080000 c801dd6c c05c4ccc f7900000
00028000
dd60: c052e4c0 00000000 40000113 00080000 c801ddcc c801dd80 c0357870
bf003978
dd80: a00c3800 00010000 00010001 c0536ea0 c801ddd0 00000002 000000d2
000000d2
dda0: c053765c c84d33e0 00000000 00000000 0000005a c902f2ab c801c000
00020a04
ddc0: c801ddec c801ddd0 c0208e50 c0357080 c052079c 0000005a 00000000
c04ca2dc
dde0: c801de04 c801ddf0 c020a228 c0208e20 c052079c 0000005a c801de24
c801de08
de00: c01cb048 c020a1a0 c85cf720 ffffffff f4000000 00000005 c801de84
c801de28
de20: c01cb8d4 c01cb00c 00000000 c04ca2dc 00000008 00000000 c902f2f8
c902f45c
de40: 00000015 c04ca2dc c902f2ab c801c000 00020a04 c801de84 00000062
c801de74
de60: c020492c c02d8fbc 20000013 ffffffff c02054a8 00000007 c801deac
c801de88
de80: c020492c c02d8fb0 c801deac 000021c4 00000028 c902f0c0 00000014
c902f36c
dea0: c801df7c c801deb0 c02056d0 c02048f4 00000000 00000000 00000000
c8014c40
dec0: c902f54c c801dec4 c902e000 c902f2ab 000021c4 c902fa34 00000013
22222222
dee0: 22222222 00000007 000021c4 00000000 00000000 c7c09cd8 c801df24
c801df08
df00: c0246e6c c02d43d4 00000007 c0201184 c801df2c c801df2c c801df6c
c801df28
df20: c0461b88 c0201138 00000000 c902f36c 22222222 22222222 22222222
22222222
df40: c01cbe08 000021c4 00020a04 0002f980 00000080 000021c4 00020a04
0002f980
df60: 00000000 c01cbe08 c801c000 00000000 c801dfa4 c801df80 c0206aa8
c0205480
df80: c022e09c c022df88 00026010 000080b4 bed98f14 00000080 00000000
c801dfa8
dfa0: c01cbc60 c0206a60 00026010 000080b4 0002f980 000021c4 00020a04
000021c4
dfc0: 00026010 000080b4 bed98f14 00000080 00000000 00000000 00000000
bed98c3c
dfe0: bed98c18 bed98c10 000081f8 00010f8c 20000010 0002f980 ffffffdf
ffffffff
Backtrace:
[<bf00396c>] (composite_setup+0x0/0xa80 [g_android]) from [<c0357870>]
(s3c_udc_
irq+0x7fc/0xf08)
[<c0357074>] (s3c_udc_irq+0x0/0xf08) from [<c0208e50>]
(handle_IRQ_event+0x3c/0x
74)
[<c0208e14>] (handle_IRQ_event+0x0/0x74) from [<c020a228>]
(handle_level_irq+0x9
4/0xec)
 r7:c04ca2dc r6:00000000 r5:0000005a r4:c052079c
[<c020a194>] (handle_level_irq+0x0/0xec) from [<c01cb048>]
(__exception_text_sta
rt+0x48/0x64)
 r5:0000005a r4:c052079c
[<c01cb000>] (__exception_text_start+0x0/0x64) from [<c01cb8d4>]
(__irq_svc+0x34
/0x80)
Exception stack(0xc801de28 to 0xc801de70)
de20:                   00000000 c04ca2dc 00000008 00000000 c902f2f8
c902f45c
de40: 00000015 c04ca2dc c902f2ab c801c000 00020a04 c801de84 00000062
c801de74
de60: c020492c c02d8fbc 20000013
ffffffff
 r6:00000005 r5:f4000000 r4:ffffffff
[<c02d8fa4>] (strcmp+0x0/0x40) from [<c020492c>] (find_sec+0x44/0x68)
 r4:00000007
[<c02048e8>] (find_sec+0x0/0x68) from [<c02056d0>] (load_module+0x25c/
0x14ec)
 r8:c902f36c r7:00000014 r6:c902f0c0 r5:00000028 r4:000021c4
[<c0205474>] (load_module+0x0/0x14ec) from [<c0206aa8>]
(sys_init_module+0x54/0x
188)
[<c0206a54>] (sys_init_module+0x0/0x188) from [<c01cbc60>]
(ret_fast_syscall+0x0
/0x2c)
 r7:00000080 r6:bed98f14 r5:000080b4 r4:00026010
Code: e3120002 12800001 e24c2020 e1a03002 (e5b3c020)
Kernel panic - not syncing: Fatal exception in interrupt
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:  http://www.***.com/ 
-~----------~----~----~----~------~----~------~--~---

3. Bad sign: Single Content apps are coming to Android

4. Getting a complete list of android native drawables

5. Launch Browser without starting a new Window

6. what is mean of "graph-based"

7. How to get System Endianess