-
Notifications
You must be signed in to change notification settings - Fork 44
high level client crash #98
Comments
Bump. Someone please look into this. |
It looks like some server on the network is issuing OC_STACK_ERROR in response to a resource discovery. I would say check the server, and attach an error handler to the client so it doesn't end up throwing a fatal exception. |
Discovery worked for me on 1.2 using high level client / server... but then hang, I will have to investigate too |
Just curious. Is security enabled by default ? |
Just curious. Is security enabled by default ? If yes, how do i get insecure version at npm install ? |
upstream and meta-oic have SECURED=0 by default on 1.2.1 and under, I aligned to that |
If you want to build with SECURED=0 you have to build iotivity externally, then export OCTBSTACK_CFLAGS and OCTBSTACK_LIBS. |
Thanks for confirming. I think these two were the issues. I ll test and update soon. |
Did the following steps.
http://www.gnu.org/software/gdb/bugs/. Thread 1 "node" received signal SIGSEGV, Segmentation fault. |
@gabrielschulhof, please help me set this up. |
Forgot to add ROUTING_EP. My bad. |
Client crashes with the following issue.
{"devAddr":{"adapter":2,"flags":0,"ifindex":0,"port":0,"addr":""},"addr":{"adapter":2,"flags":0,"ifindex":0,"port":0,"addr":""},"connType":131072,"identity":[],"result":255,"sequenceNumber":0,"resourceUri":"/oic/res","rcvdVendorSpecificHeaderOptions":[]}
/home/sanjeev/source/jlr/node_modules/iotivity-node/lib/csdk.js:39
throw theError;
^
Error: findResources: Unexpected response
The text was updated successfully, but these errors were encountered: