On Tue, Apr 9, 2013 at 8:40 PM, Rodolph Perfetta <[email protected]> wrote: > Which CPU are you running the armeabi version on?
I'm trying it on a Froyo (armeabi) device set up on the standard android emulator. > V8 supports ARMv6 + VFPv2 so it doesn't have to be on v7. If you are looking at pre ARMv6 support then > as you said you should disable V8 for this target (v3.9 should work but not > future versions). Right. Ideally it's 3.9 I'd like to make work - but I've had no luck at all. > The trace you sent looks like it maybe an arm/thumb mismatch, you could add > -mthumb to the makefile and check. Alas -mthumb didn't help :( On Tuesday, 9 April 2013 20:58:30 UTC+1, Rodolph Perfetta wrote: > > I should probably have asked before, but what makes you think the crash > comes from V8? Do you have a more precise trace? > I can build our library with v8 linked in, or not. The version without v8 linked in works perfectly. The version with v8 dies during the shared library load. This suggests to me that there is some binary incompatibility between the two. I'd *guess* that there is some initialisation code in the v8 lib that is called at load time and that's somehow causing the crash, but the gdb backtrace is the textbook definition of unhelpful. Thanks again, Robin -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
