paddybyers / anode Goto Github PK
View Code? Open in Web Editor NEWAndroid framework for node.js applications
License: Other
anode's People
Stargazers
Watchers
Forkers
truedat101 sequoiar codefridge infil00p log111 no9 nomadlibra val9 fengdi palvarez89 gotomypc sgithens alfonsodev p0sixninja namuol feichh fabei jdorner pmorau maj21 bryanwang doowb gongfupanada ninjablocks amolmk ashirvad ctiao tuomas56 ibank nelsonomuto dromescu sanyaade-teachings uplusplus iyogeshjoshi xpatch qyqx lifuzu webinos eiriklv armen138 yangchengit pmrocha technology-hatchery mmcomp b4bass gogamoga marlncpe pavandubba modu sprime01 bitbay syejiang webcraft13 jarshchen sanyaade-iot abdullah353 yanglichuan sn3g14 robertomalatesta cannedfish feinfugk johnsonlee coinhelper lknlfy yeqingyu sobolsigizmund adityapedagada vaginessa charlieyqin jackyglony morristech hhy5277 titans-halo hixio-mh ostosh tioidem iq-scmanode's Issues
Node now builds on android
Is there refactoring required now @modeswitch has landed this?
https://gist.github.com/modeswitch/114c9bd55d800df242a2
Can not restart a node.js instance.
Hi
To start a node.js instance is ok, but stop and then restart it will always fail.
The below is the logcat log.
01-13 23:52:47.909: V/libjninode(20777): Java_org_meshpoint_anode_RuntimeNative_create ent
01-13 23:52:47.909: V/libjninode(20777): Java_org_meshpoint_anode_RuntimeNative_create ret
01-13 23:52:47.909: V/anode::Isolate(20777): Isolate.run(): setting context
01-13 23:52:47.909: V/bridge-core(20777): Env::setupEnv(): ent
01-13 23:52:47.909: V/bridge-core(20777): Env::initThread(): ent
01-13 23:52:47.909: V/bridge-core(20777): Env::initThread(): ret
01-13 23:52:47.909: V/bridge-core(20777): Env::setupEnv(): ret
01-13 23:52:47.909: V/anode::Isolate(20777): Isolate.run(): set context
01-13 23:52:47.909: V/anode::Isolate(20777): stateState: state = 2
01-13 23:52:47.909: V/libjninode(20777): Java_org_meshpoint_anode_RuntimeNative_start: ent
01-13 23:52:47.909: V/libjninode(20777): getNativeArgs: ent
01-13 23:52:47.909: V/libjninode(20777): getNativeArgs: ret 2
01-13 23:52:48.349: V/libjninode(20777): Java_org_meshpoint_anode_RuntimeNative_start: ret 1
01-13 23:52:48.349: V/anode::Isolate(20777): stateState: state = 4
Did anyone experience this problem?
Thank you.
bridge.node separated into libbridge.so and bridge.node
I'm not sure if this is possible, but can we separate the current bridge.node into 2 libraries libbridge.so (for Java loading) and bridge.node (for nodejs loading).
Doing so will allow us to load libbridge with the "regular" Java method System.loadLibrary so that we're not tied to the filesystem layout of /data/data which is widely supported, but technically not a requirement of an android system.
If you can make the c and c++ section work, I'll add in the Java support.
porting node.js v0.8.x on Android
Did you have plan to run node.js v0.8.x on Android? And, could you show me some clue to port node.js to Android?
- compile node.js on Android natively
- implement jni wrapper of node.js
- ...
Any tutorial or example ?
Hi
I'd like to create an application using anode but i can't find any tutorial or demo or example. Any example?
Anode? Node on Android? Guidance welcome
As mentioned in #28 it is now reasonably easy to build Android for Node (my own flavor of instructions are at http://www.goland.org/nodejsonandroid/). Now, it's not all fun and games. There are still basic things I'm trying to figure out such as nodejs/node-gyp#515. But it looks like you can get there from here.
The project I'm working on (http://www.thaliproject.org) wants to create a run time environment that uses HTML5 as the front end and node.js on the back end and runs on Android, iOS, Windows Desktop, Windows Runtime (read: store apps and phone) as well as Mac and Linux. Yes, this does smell a little bit like node-webkit but we explicitly don't want the HTML 5 front end and the Node.JS code to be tightly bound. We are very happy with a model in which HTML5 runs in a browser or web view and the Node.js code runs in a completely separate process/thread that has its own life cycle. We need this because in places like mobile we want the node.js program to hang out forever (only really feasible today with Android) receiving requests and handling them. In our case we are using node.js to house PouchDB and handle synching data in our peer to peer web.
Which, finally, brings me to anode. I'm trying to figure out how to think about anode. I think our needs are actually less ambitious than anode. We would be perfectly happy just starting up a node.js process and letting it go. If the HTML 5 front end needs to talk to the node.js process then we are happy to do that over a localhost http connection. We even have a simple plan to use shared secrets to secure the connection so other apps on the same device can't sneak in.
Given our goals is anode what we should be looking at? Or would we be better off just wrapping up node on Android with a nice little spawn event inside of a Java wrapper and calling it a day? [1]
[1] And yes, I realize it won't be that easy. We'll need to handle life cycle events and surface them in node so it can gracefully shut itself off or know when there is no network connectivity. Our thinking is to expose these as standard events in node that would look the same on all of our platforms.
Runtime error, FileNotFoundException: libjninode.so
I am getting the following error when I am trying to run anode on my Transformer prime running Android 4.0.3.
Is Anode packaging the .so files as part of the .apk, then extracting them to the filesystem at runtime as executables ?
If so, can an non rooted device write to the standard library location ?
04-25 06:25:27.224: D/TextView(1523): Constructor - Got appearance for textColorPrimaryInverse
04-25 06:25:27.224: D/TextView(1523): Constructor -- Got mEditTextBackgroundColor
04-25 06:25:57.744: V/anode::RuntimeNative(1523): extractLib: copying library
04-25 06:25:57.744: V/anode::RuntimeNative(1523): init: unable to write library to file: java.io.FileNotFoundException: libjninode.so
04-25 06:25:57.744: V/anode::AnodeActivity(1523): initRuntime: exception: org.meshpoint.anode.Runtime$InitialisationException: java.io.FileNotFoundException: libjninode.so; cause: java.io.FileNotFoundException: libjninode.so
04-25 06:25:57.744: V/anode::AnodeActivity(1523): isolate start: exception: org.meshpoint.anode.Runtime$IllegalStateException: Runtime has not beed initialised; cause: null
04-25 06:41:45.824: W/dalvikvm(1523): No implementation found for native Lorg/meshpoint/anode/RuntimeNative;.nodeDispose ()V
04-25 06:41:45.824: D/dalvikvm(1523): GC_CONCURRENT freed 344K, 6% free 6575K/6983K, paused 11ms+3ms
04-25 06:41:46.194: E/System(1523): Uncaught exception thrown by finalizer
04-25 06:41:46.224: E/System(1523): java.lang.UnsatisfiedLinkError: nodeDispose
04-25 06:41:46.224: E/System(1523): at org.meshpoint.anode.RuntimeNative.nodeDispose(Native Method)
04-25 06:41:46.224: E/System(1523): at org.meshpoint.anode.Runtime.finalize(Runtime.java:120)
04-25 06:41:46.224: E/System(1523): at java.lang.Daemons$FinalizerDaemon.doFinalize(Daemons.java:182)
04-25 06:41:46.224: E/System(1523): at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:168)
04-25 06:41:46.224: E/System(1523): at java.lang.Thread.run(Thread.java:856)
Fix UnsatisfiedLinkError when loading libjninode.so from apk
In NDK r8b and r8c, we got an error during the blank app execution:
VERBOSE/anode::RuntimeNative(21348): init: unable to load library: java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1290]: 113 cannot locate '__gnu_thumb1_case_uqi'.
The fix is described here:
https://github.com/ted0000/koccalink/commit/fb1c481e0fd68f5c4aecdc7488c5defe8c0a627f#commitcomment-2318630
build failed on mac osx 10.7
OS : mac osx 10.7
xcode: 4.2
openssl: 1.0.0e
I follow the build instructions in wiki
https://github.com/paddybyers/anode/wiki/Build
But it could not work for me.First, If i set NDK_MODULE_PATH as you say
export NDK_MODULE_PATH=/anode:/anode/anode
Then ndk-build failed with message
Android NDK: /Users/apple/programming/js/node-js/anode/anode/libnode/jni/Android.mk: Cannot find module with tag 'deps/c-ares' in import path
Android NDK: Are you sure your NDK_MODULE_PATH variable is properly defined ?
Android NDK: The following directories were searched:
Android NDK:
/Users/apple/programming/js/node-js/anode/anode/libnode/jni/Android.mk:42: *** Android NDK: Aborting. . Stop.
Then ,i changed NDK_MODULE_PATH to
export NDK_MODULE_PATH=/anode:/anode/anode:/anode/node
Then ndk-build failed again,but with message
Compile++ thumb : node <= node.cc
In file included from /Users/apple/programming/js/node-js/anode//node/src/node.cc:76:
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:29:25: error: openssl/ssl.h: No such file or directory
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:30:25: error: openssl/err.h: No such file or directory
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:31:25: error: openssl/evp.h: No such file or directory
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:32:25: error: openssl/pem.h: No such file or directory
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:33:26: error: openssl/x509.h: No such file or directory
/Users/apple/programming/js/node-js/anode//node/src/node_crypto.h:34:26: error: openssl/hmac.h: No such file or directory
But i have installed openssl on my mac machine,and openssl/ssl.h,openssl/err.h etc these files are already in /usr/include/openssl,why ndk-build can not find them?
Can you help me?Thanks a lot.
Would be convenient if console.log wrote to Android's LOGCAT
It would be convenient if console.log and related functions wrote to Android's LOGCAT by default.
See android/log.h in the NDK.
Thread pooling not working in libuv, calling uv_run(uv_default_loop()) fixes
When compiling node-sqlite3 for anode, db connections weren't being successfully opened. Investigating further, it seemed that the the "after" callback in uv_queue_work wasn't being called. Adding uv_run(uv_default_loop()) fixes both this test code and the sqlite code.
This code shows the error:
#include <node.h>
#include <v8.h>
#include <android/log.h>
#define APPNAME "HELLOWORLD"
using namespace v8;
static int timesFinished = 0;
void AsyncWork(uv_work_t* req) {
__android_log_print(ANDROID_LOG_VERBOSE, APPNAME, "In Async Work");
timesFinished++;
}
void AfterAsync(uv_work_t* req) {
__android_log_print(ANDROID_LOG_VERBOSE, APPNAME, "Finished Async Work");
timesFinished++;
// be nice and clean up
delete req;
req = NULL;
}
Handle<Value> Method(const Arguments& args) {
HandleScope scope;
uv_work_t * req = new uv_work_t();
int status = uv_queue_work(uv_default_loop(), req, AsyncWork, AfterAsync);
__android_log_print(ANDROID_LOG_VERBOSE, APPNAME, "uv_queue_work status %d", status);
// I Shouldn't have to call this... but calling it fixes this code AND SQLITE3
uv_run(uv_default_loop());
__android_log_print(ANDROID_LOG_VERBOSE, APPNAME, "work count should be 2 %d", timesFinished);
return scope.Close(String::New("something worked"));
}
void init(Handle<Object> target) {
target->Set(String::NewSymbol("test"), FunctionTemplate::New(Method)->GetFunction());
}
NODE_MODULE(asyncfail, init)It would appear that libuv's event loop (?) isn't being started, and this problem would be fixed by adding a call to uv_run(...) in the initialization somewhere.
UnsatisfiedLinkError when running node.js script
I'd put together a very simple "Hello world" script to try out Anode with. It's really nothing more than a console.log( ), but it's crashing with:
E/AndroidRuntime(19217): FATAL EXCEPTION: IntentService[:anode.AnodeService]
E/AndroidRuntime(19217): java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1306]: 144 cannot locate 'SSLv2_method'...
E/AndroidRuntime(19217):
E/AndroidRuntime(19217): at java.lang.Runtime.load(Runtime.java:340)
E/AndroidRuntime(19217): at java.lang.System.load(System.java:524)
E/AndroidRuntime(19217): at org.meshpoint.anode.RuntimeNative.init(RuntimeNative.java:61)
E/AndroidRuntime(19217): at org.meshpoint.anode.Runtime.(Runtime.java:116)
E/AndroidRuntime(19217): at org.meshpoint.anode.Runtime.initRuntime(Runtime.java:49)
E/AndroidRuntime(19217): at org.meshpoint.anode.AnodeService.initRuntime(AnodeService.java:86)
E/AndroidRuntime(19217): at org.meshpoint.anode.AnodeService.onHandleIntent(AnodeService.java:105)
E/AndroidRuntime(19217): at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:65)
E/AndroidRuntime(19217): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(19217): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(19217): at android.os.HandlerThread.run(HandlerThread.java:60)
Did OpenSSL change out from under you, perhaps?
Building ANode
I am trying to build the anode project and I have a few questions as well as running into an error.
I am building the project under Eclipse Juno, with an updated SDK r17 and NDK r8d running on OS/X.
What I have done so far.
I built the node project in , which builds and runs fine. In I then did a git clone https://github.com/paddybyers/anode.git and imported any existing projects into Eclipse that existed in
This resulted in the following projects, app, bridge-java, bridge-stub-generator, libnode, and sdk.
Most all the projects compiled fine except for bridge-stub-generator which failed because of the following error but I am assuming that the bridge-stub-generator is not a run-time requirement.
The constructor InterfaceManager(ClassLoader, boolean) is undefined StubGen.java /bridge-stub-generator/src/org/meshpoint/anode/stub/util line 153*
When I try to run App, I get the following error.
[2013-04-20 23:39:38 - Dex Loader] Unable to execute dex: Multiple dex files define Lorg/meshpoint/anode/AndroidContext;
[2013-04-20 23:39:38 - app] Conversion to Dalvik format failed: Unable to execute dex: Multiple dex files define Lorg/meshpoint/anode/AndroidContext;
The question I have is, how is the node project connected as a dependency to the ANode project ?
Thank you
John Gentilin
Root Access For Native Modules
Hi
I see there is a requirement to put the addons into
/data/data/org.meshpoint.anode/app/module/
This requires root access to the phone.
Any idea when it will be resolved or a clue on what prevented the modules being placed on the SDCARD for example?
Thanks and loved the talk @ LXJS BTW.
how to remove views in android dynamically on swipe without using listview or recyclerview?
Need help, remove views in android dynamically on swipe without using listview or recyclerview?
Building For ICS 4.0.4 Runtime Error
Trying to deploy on ICS to leverage USB Support.
Seems to compile fine with
Android SDK Tools REV 20.0.3
Android SDK Platform-tools REV 14
SDK Platform API 15
But executing I get
Cannot load library: reloc_library[1286]: 1702 cannot locate '__aeabi_ldiv0'...
In RuntimeNative.java
On-line
System.load(runtimePath + '/' + RUNTIME_LIBRARY);
From what I can glean its a link issue but I can't make much headway into it and would appreciate a pointer if you have one.
Ports not being released on stop?
Hi,
It seems to me that the listening sockets are kept open after i stop an isolate, until I force stop the app through the app settings.
This can cause EADDRINUSE errors, when a server is started again.
cheers
where to download latest version anode apk
I just found anode-26-11-11.apk. It is latest version?
TarExtractor not handling directories correctly?
Im trying to use the action "org.meshpoint.anode.INSTALL", I noticed the org.meshpoint.anode.util.TarExtractor does not deal with directories corretly.
My temp solution for this is as follows (~l.60f):
if (entry.isDirectory()) {
entryFile.mkdir();
} else {
FileOutputStream fos = new FileOutputStream(entryFile);
BufferedOutputStream bos = new BufferedOutputStream(fos);
while ((count = tis.read(buf)) != -1) {
bos.write(buf, 0, count);
}
bos.flush();
bos.close();
}
Maybe you want to take a look at this.
cheers
LIBRARY_PATH is error
LIBRARY_PATH should be
private static String LIBRARY_PATH = "/data/data/" + PACKAGE_NAME + "/lib";
It is not in app folder on my i9100.
No javascript console in the browser
I have compiled anode with node v0.6-android, my device is a pandaboard ES running linaro android 4.1.1. The compilation was successful, and I installed the .apk in the android OS.
For testing it, I use a hello world script :
var http = require('http');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/html'});
res.end('Hello World\n');
}).listen(1337, '127.0.0.1');
console.error('Server running at http://127.0.0.1:1337/');
I put the path to the script file in the application window and click "start", then I open my browser and tap 172.0.0.1:1337. Now the problem is that I have the 'Hello Word' message in the page without the javascript console log. I have enabled the option "show javascript console", but it doesn't appear. I can even read the console in other web pages.
So what could be the problem ?
How to get data using web sockets in android NDK?
Hi,
I am new to Android mobile app development.
I would like to know how we can get data using web sockets in android NDK?
libjninode crush
When I run anode with "-e cmdline /sdcard/webrtc/app.js", libjninode.so crushed:
I/DEBUG (29615): handle_request(16)
I/DEBUG (29615): check process 29544 name:meshpoint.anode
I/DEBUG (29615): BOOM: pid=29544 uid=10097 gid=10097 tid=29614
I/DEBUG (29615): [OnPurpose Redunant in preset_info] pid: 29544, tid: 29614, name: Thread-1644 >>> org.meshpoint.anode <<<
I/DEBUG (29615): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG (29615): Build fingerprint: 'alps/mt6589_phone_evdo/mt6589_phone_evdo:4.2.1/JOP40D/1363305743:eng/release-keys'
I/DEBUG (29615): pid: 29544, tid: 29614, name: Thread-1644 >>> org.meshpoint.anode <<<
I/DEBUG (29615): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG (29615): r0 00000000 r1 00000027 r2 deadbfff r3 40067f58
I/DEBUG (29615): r4 00000000 r5 55cf8a54 r6 400b0c68 r7 400a1e08
I/DEBUG (29615): r8 55cf8b58 r9 55bf8fb4 sl 54b28788 fp 55cf8a7c
I/DEBUG (29615): ip 55cf8a28 sp 55cf8a50 lr 4006985c pc 40062a80 cpsr 60000010
I/DEBUG (29615):
I/DEBUG (29615): backtrace:
I/DEBUG (29615): #00 pc 0002aa80 /system/lib/libc.so
I/DEBUG (29615): #01 pc 0001250c /system/lib/libc.so
I/DEBUG (29615): #02 pc 000129d0 /system/lib/libc.so
I/DEBUG (29615): #03 pc 0001e78c /system/lib/libc.so (dlfree+76)
I/DEBUG (29615): #04 pc 0001af3c /system/lib/libc_malloc_debug_mtk.so (mtk_free+240)
I/DEBUG (29615): #05 pc 0000dea0 /system/lib/libc.so (free+24)
I/DEBUG (29615): #06 pc 0003d2f7 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): #07 pc 0003d55f /data/data/org.meshpoint.anode/app/libjninode.so (Java_org_meshpoint_anode_RuntimeNative_start+50)
I/DEBUG (29615): #08 pc 0001e9d0 /system/lib/libdvm.so (dvmPlatformInvoke+112)
I/DEBUG (29615): #09 pc 0004e221 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+500)
I/DEBUG (29615): #10 pc 00050597 /system/lib/libdvm.so (dvmResolveNativeMethod(unsigned int const*, JValue*, Method const*, Thread*)+174)
I/DEBUG (29615): #11 pc 00027da0 /system/lib/libdvm.so
I/DEBUG (29615): #12 pc 0002bcfc /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+180)
I/DEBUG (29615): #13 pc 00061499 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+272)
I/DEBUG (29615): #14 pc 000614c3 /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
I/DEBUG (29615): #15 pc 00055b3d /system/lib/libdvm.so
I/DEBUG (29615): #16 pc 0000f66c /system/lib/libc.so (__thread_entry+80)
I/DEBUG (29615):
I/DEBUG (29615): stack:
I/DEBUG (29615): 55cf8a10 ffffffff
I/DEBUG (29615): 55cf8a14 00000000
I/DEBUG (29615): 55cf8a18 55cf8a4c [stack:29614]
I/DEBUG (29615): 55cf8a1c 55cf8a28 [stack:29614]
I/DEBUG (29615): 55cf8a20 4006985c /system/lib/libc.so (_fwalk+72)
I/DEBUG (29615): 55cf8a24 4006798c /system/lib/libc.so (__sflush+12)
I/DEBUG (29615): 55cf8a28 40067f58 /system/lib/libc.so (_cleanup)
I/DEBUG (29615): 55cf8a2c 43040000
I/DEBUG (29615): 55cf8a30 55cf8a54 [stack:29614]
I/DEBUG (29615): 55cf8a34 400b0c68
I/DEBUG (29615): 55cf8a38 400a1e08 /system/lib/libc.so
I/DEBUG (29615): 55cf8a3c 55cf8b58 [stack:29614]
I/DEBUG (29615): 55cf8a40 55cf8a7c [stack:29614]
I/DEBUG (29615): 55cf8a44 55cf8a50 [stack:29614]
I/DEBUG (29615): 55cf8a48 df0027ad
I/DEBUG (29615): 55cf8a4c 00000000
I/DEBUG (29615): #00 55cf8a50 410d6838 [heap]
I/DEBUG (29615): 55cf8a54 fffffbdf
I/DEBUG (29615): 55cf8a58 55959357 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8a5c 55cf8ae0 [stack:29614]
I/DEBUG (29615): 55cf8a60 55959357 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8a64 400b0c68
I/DEBUG (29615): 55cf8a68 55cf8ae0 [stack:29614]
I/DEBUG (29615): 55cf8a6c 55959357 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8a70 55cf8aa4 [stack:29614]
I/DEBUG (29615): 55cf8a74 55cf8a80 [stack:29614]
I/DEBUG (29615): 55cf8a78 4004a510 /system/lib/libc.so
I/DEBUG (29615): 55cf8a7c 40062a08 /system/lib/libc.so
I/DEBUG (29615): #01 55cf8a80 00001099
I/DEBUG (29615): 55cf8a84 00000003
I/DEBUG (29615): 55cf8a88 55cf8ae0 [stack:29614]
I/DEBUG (29615): 55cf8a8c 55959357 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8a90 400b0c68
I/DEBUG (29615): 55cf8a94 400b0c68
I/DEBUG (29615): 55cf8a98 55cf8ad4 [stack:29614]
I/DEBUG (29615): 55cf8a9c 55cf8aa8 [stack:29614]
I/DEBUG (29615): 55cf8aa0 4004a9d4 /system/lib/libc.so
I/DEBUG (29615): 55cf8aa4 4004a46c /system/lib/libc.so
I/DEBUG (29615): #02 55cf8aa8 00100000
I/DEBUG (29615): 55cf8aac 00001000
I/DEBUG (29615): 55cf8ab0 00000001
I/DEBUG (29615): 55cf8ab4 55959357 /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8ab8 5595935f /data/data/org.meshpoint.anode/app/libjninode.so
I/DEBUG (29615): 55cf8abc 00000003
I/DEBUG (29615): 55cf8ac0 400b0c68
I/DEBUG (29615): 55cf8ac4 55cf8c3c [stack:29614]
I/DEBUG (29615): 55cf8ac8 55cf8b34 [stack:29614]
I/DEBUG (29615): 55cf8acc 55cf8ad8 [stack:29614]
I/DEBUG (29615): 55cf8ad0 40056790 /system/lib/libc.so (dlfree+80)
I/DEBUG (29615): 55cf8ad4 4004a9b8 /system/lib/libc.so
I/DEBUG (29615):
I/DEBUG (29615): memory near r3:
I/DEBUG (29615): 40067f38 e1d540fe e3500000 0afffff8 e1a00005 [email protected].........
I/DEBUG (29615): 40067f48 eb0000e4 e1a00004 e89da830 00046014 ........0....`..
I/DEBUG (29615): 40067f58 e59f0014 e1a0c00d e92dd800 e24cb004 ..........-...L.
I/DEBUG (29615): 40067f68 e79f0000 e89d6800 ea000627 00046010 .....h..'....`..
I/DEBUG (29615): 40067f78 e1a0c00d e59f0084 e92dd878 e24cb004 ........x.-...L.
I/DEBUG (29615):
I/DEBUG (29615): memory near r5:
I/DEBUG (29615): 55cf8a34 400b0c68 400a1e08 55cf8b58 55cf8a7c h..@[email protected]|..U
I/DEBUG (29615): 55cf8a44 55cf8a50 df0027ad 00000000 410d6838 P..U.'......8h.A
I/DEBUG (29615): 55cf8a54 fffffbdf 55959357 55cf8ae0 55959357 ....W..U...UW..U
I/DEBUG (29615): 55cf8a64 400b0c68 55cf8ae0 55959357 55cf8aa4 [email protected]
I/DEBUG (29615): 55cf8a74 55cf8a80 4004a510 40062a08 00001099 ...U...@.*.@....
I/DEBUG (29615):
I/DEBUG (29615): memory near r6:
I/DEBUG (29615): 400b0c48 00001000 00001000 00040000 00200000 .............. .
I/DEBUG (29615): 400b0c58 00000003 4002b4cc 00000000 40f4ac9c .......@.......@
I/DEBUG (29615): 400b0c68 00000000 040b8a98 0008156a 00000128 ........j...(...
I/DEBUG (29615): 400b0c78 00020fd8 40023000 55ae6658 55df9000 [email protected]
I/DEBUG (29615): 400b0c88 00200000 00000e2a 1e150ca8 00000000 .. .*...........
I/DEBUG (29615):
I/DEBUG (29615): memory near r7:
I/DEBUG (29615): 400a1de8 6174736d 00006574 656c6572 5f657361 mstate..release_
I/DEBUG (29615): 400a1df8 73756e75 735f6465 656d6765 0073746e unused_segments.
I/DEBUG (29615): 400a1e08 5f6b746d 616d6c64 636f6c6c 6265645f mtk_dlmalloc_deb
I/DEBUG (29615): 400a1e18 00006775 3d3d3d3d 3d3d3d3d 3d3d3d3d ug..============
I/DEBUG (29615): 400a1e28 5245203d 20524f52 4e554843 3028204b = ERROR CHUNK (0
I/DEBUG (29615):
I/DEBUG (29615): memory near r8:
I/DEBUG (29615): 55cf8b38 5593203b 55cf8b64 00000001 55bf9000 ; .Ud..U.......U
I/DEBUG (29615): 55cf8b48 00100000 00001000 00000000 00000000 ................
I/DEBUG (29615): 55cf8b58 40045ea0 558222f7 fffffffc 55cf8ba8 .^.@.".U.......U
I/DEBUG (29615): 55cf8b68 55cf8c54 55cf8b78 55932043 40046908 T..Ux..UC .U.i.@
I/DEBUG (29615): 55cf8b78 5593203b 558f1c55 55cf9008 558f20cb ; .UU..U...U. .U
I/DEBUG (29615):
I/DEBUG (29615): memory near r9:
I/DEBUG (29615): 55bf8f94 43360ca8 00000000 433748c8 55bf8fd4 ..6C.....H7C...U
I/DEBUG (29615): 55bf8fa4 54465b5a 4e348690 00000000 00000000 Z[FT..4N........
I/DEBUG (29615): 55bf8fb4 55ab5bc8 00000000 1d600005 55bf9000 .[.U......`....U
I/DEBUG (29615): 55bf8fc4 00000000 4e348bc8 54465b5a 00000000 ......4NZ[FT....
I/DEBUG (29615): 55bf8fd4 00000000 00000000 55ab5bc8 00000000 .........[.U....
I/DEBUG (29615):
I/DEBUG (29615): memory near sl:
I/DEBUG (29615): 54b28768 00000000 559a7531 00000000 00000453 ....1u.U....S...
I/DEBUG (29615): 54b28778 4fa5514c 55bf8fb4 4e348bc8 5447e000 LQ.O...U..4N..GT
I/DEBUG (29615): 54b28788 55ab5bc8 00000000 55cf8d90 00000000 .[.U.......U....
I/DEBUG (29615): 54b28798 55cf8dc4 00000011 00000000 40b4eb40 ...U........@..@
I/DEBUG (29615): 54b287a8 00000000 00000000 4d692770 55bf1300 ........p'iM...U
I/DEBUG (29615):
I/DEBUG (29615): memory near fp:
I/DEBUG (29615): 55cf8a5c 55cf8ae0 55959357 400b0c68 55cf8ae0 [email protected]
I/DEBUG (29615): 55cf8a6c 55959357 55cf8aa4 55cf8a80 4004a510 W..U...U...U...@
I/DEBUG (29615): 55cf8a7c 40062a08 00001099 00000003 55cf8ae0 .*[email protected]
I/DEBUG (29615): 55cf8a8c 55959357 400b0c68 400b0c68 55cf8ad4 W..Uh..@[email protected]
I/DEBUG (29615): 55cf8a9c 55cf8aa8 4004a9d4 4004a46c 00100000 ...U...@l..@....
I/DEBUG (29615):
I/DEBUG (29615): memory near ip:
I/DEBUG (29615): 55cf8a08 0000000a 400ae208 ffffffff 00000000 .......@........
I/DEBUG (29615): 55cf8a18 55cf8a4c 55cf8a28 4006985c 4006798c L..U(..U\[email protected].@
I/DEBUG (29615): 55cf8a28 40067f58 43040000 55cf8a54 400b0c68 [email protected]..@
I/DEBUG (29615): 55cf8a38 400a1e08 55cf8b58 55cf8a7c 55cf8a50 [email protected]|..UP..U
I/DEBUG (29615): 55cf8a48 df0027ad 00000000 410d6838 fffffbdf .'......8h.A....
I/DEBUG (29615):
I/DEBUG (29615): memory near sp:
I/DEBUG (29615): 55cf8a30 55cf8a54 400b0c68 400a1e08 55cf8b58 T..Uh..@[email protected]
I/DEBUG (29615): 55cf8a40 55cf8a7c 55cf8a50 df0027ad 00000000 |..UP..U.'......
I/DEBUG (29615): 55cf8a50 410d6838 fffffbdf 55959357 55cf8ae0 8h.A....W..U...U
I/DEBUG (29615): 55cf8a60 55959357 400b0c68 55cf8ae0 55959357 [email protected]
I/DEBUG (29615): 55cf8a70 55cf8aa4 55cf8a80 4004a510 40062a08 ...U...U...@.*.@
I/DEBUG (29615):
I/DEBUG (29615): code around pc:
I/DEBUG (29615): 40062a60 1afffffb e594c014 e35c0000 0a000018 ..........\.....
I/DEBUG (29615): 40062a70 e30b2fff e3a01027 e34d2ead e3a04000 ./..'.....M..@..
I/DEBUG (29615): 40062a80 e5421552 ebffef1a e3a01006 ebfff3cb R.B.............
I/DEBUG (29615): 40062a90 e24b1024 e3a03201 e1a02001 e3a00006 $.K..2... ......
I/DEBUG (29615): 40062aa0 e50b301c e50b4024 e50b4020 ebfff1bb .0..$@.. @......
I/DEBUG (29615):
I/DEBUG (29615): code around lr:
I/DEBUG (29615): 4006983c 4a000009 e1d430fc e1a00004 e2455001 ...J.0.......PE.
I/DEBUG (29615): 4006984c e2844054 e3530000 da000001 e12fff37 [email protected]./.
I/DEBUG (29615): 4006985c e1866000 e3750001 1afffff5 e5988000 .`....u.........
I/DEBUG (29615): 4006986c e3580000 1affffee e1a00006 e89da9f8 ..X.............
I/DEBUG (29615): 4006987c 00044754 e1a0c00d e92dddf0 e24cb004 TG........-...L.
I/DEBUG (29615):
I/DEBUG (29615): memory map around fault addr deadbaad:
I/DEBUG (29615): be9d4000-be9f5000 [stack]
I/DEBUG (29615): (no map for address)
I/DEBUG (29615): ffff0000-ffff1000 [vectors]
may be it's a memory leak.
building error
I followed as https://github.com/paddybyers/anode/wiki/build
but i met a compile error as below:
/home/david/NDKs/android-ndk-r9/toolchains/arm-linux-androideabi-4.6/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ -MMD -MP -MF ./obj/local/armeabi/objs/bridge/src/Env.o.d -fpic -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -march=armv5te -mtune=xscale -msoft-float -fno-exceptions -fno-rtti -mthumb -Os -g -DNDEBUG -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -Ibridge/src -I./../node/src -I./../node/deps/v8/include -I./../node/deps/uv/include -I/home/david/NDKs/android-ndk-r9/sources/cxx-stl/system/include -Ibridge -DANDROID -D__POSIX__ -DBUILDING_NODE_EXTENSION -include sys/select.h -Wa,--noexecstack -Wformat -Werror=format-security -I/home/david/NDKs/android-ndk-r9/platforms/android-14/arch-arm/usr/include -c bridge/src/Env.cpp -o ./obj/local/armeabi/objs/bridge/src/Env.o
bridge/src/Env.cpp: In member function 'int bridge::Env::initV8()':
bridge/src/Env.cpp:142:16: error: 'class node::Isolate' has no member named 'setExitHandler'
make: *** [obj/local/armeabi/objs/bridge/src/Env.o] Error 1
Pls let me know what I shoud do.
build bridge failed(no setExitHandler) on 'master-isolate-android'
some errors came out when I checked out 'master-isolate-android' :
$ ndk-build NDK_PROJECT_PATH=. NDK_APPLICATION_MK=Application.mk
Install : libjninode.so => libs/armeabi/libjninode.so
Compile++ thumb : bridge <= Env.cpp
bridge/src/Env.cpp: In member function 'int bridge::Env::initV8()':
bridge/src/Env.cpp:142:16: error: 'class node::Isolate' has no member named 'setExitHandler'
make: *** [obj/local/armeabi/objs/bridge/src/Env.o] Error 1
apk-Build
I'm not really into Android development. So I wanted to ask for a pre-built App-package. - would that be possible? T
hanks.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.