[dev] segmentation fault while running simpleclient

2015-03-18 Thread Keane, Erich
Hi Han-Lin- This is a bug we've seen before. It is caused because the Android compilation options are different enough from the shared-object compilation options, resulting in some incompatible allocations in std::string inside of this object. We have 2 possible solutions. First, you can move

[dev] segmentation fault while running simpleclient

2015-03-18 Thread Han-Lin Li
I used valgrind to trace segmentation fault point. It crashed in destructor of OCRepresentation. Anyone have any idea? ==6406== Thread 3: ==6406== Invalid free() / delete / delete[] / realloc() ==6406==at 0x481A50C: free (vg_replace_malloc.c:473) ==6406==by 0x1B472B: _M_dispose (basic_str

[dev] segmentation fault while running simpleclient

2015-03-03 Thread Han-Lin Li
I pulled the newest master branch from git, but I got a new crash from simpleserver ./simpleserver Usage : simpleserver Default - Non-secure resource and notify all observers 1 - Non-secure resource and notify list of observers 2 - Secure resource and notify all observers 3 - Se

[dev] segmentation fault while running simpleclient

2015-03-02 Thread Lankswert, Patrick
e: [dev] segmentation fault while running simpleclient > > I use master release because I can't compile CA branch to android. > simpleclient and simpleserver of master release works on Linux platform > without any error. > But, their put() function didn't work on androi

[dev] segmentation fault while running simpleclient

2015-02-27 Thread Han-Lin Li
I use master release because I can't compile CA branch to android. simpleclient and simpleserver of master release works on Linux platform without any error. But, their put() function didn't work on android. 2015-02-27 2:29 GMT+08:00 Keane, Erich : > Are you on 0.9.0 master or connectivity abstrac

[dev] segmentation fault while running simpleclient

2015-02-27 Thread Han-Lin Li
I used 0.9.0 release. 2015-02-27 1:39 GMT+08:00 Keane, Erich : > I don't see anything that is obvious on this one. Can you tell me what > commit-id you are working off of? Perhaps I can see if I can reproduce > it. > > Thanks! > -Erich > > On Thu, 2015-02-26 at 19:10 +0800, Han-Lin Li wrote: >>

[dev] segmentation fault while running simpleclient

2015-02-26 Thread Lenahan, Charlie
You should be able to run adb shell dumpsys dropbox SYSTEM_TOMBSTONE ?print > foo.crash that will give you the crash dump. You can then get a stack trace ndk-stack -dump foo.crash -sym /path/to/your/simpleclient/obj/local/target_abi/ Charlie Lenahan | Software Engineer | I

[dev] segmentation fault while running simpleclient

2015-02-26 Thread Han-Lin Li
I run simpleclient and simpleserver by adb and get a segmentation fault Here is the debug message Getting Light Representation... v:1 t:1 tkl:8 c:1 id:65355 o: [ 7:'\xB5\x95', 11:'a', 11:'light' ] Jan 16 00:49:27 DEBG bytes_written 23 Jan 16 00:49:27 DEBG coap_read: discarded invalid frame

[dev] segmentation fault while running simpleclient

2015-02-26 Thread Keane, Erich
Did you say "adb" meaning Android? If so, support for Android on Master is pretty poor in the first place, and even worse in 0.9.0. At the moment the Android-API branch is pretty good, but you'll have to pull from git. On Fri, 2015-02-27 at 02:25 +0800, Han-Lin Li wrote: > I used 0.9.0 relea

[dev] segmentation fault while running simpleclient

2015-02-26 Thread Keane, Erich
Are you on 0.9.0 master or connectivity abstraction? I just did a pull of that one, so I'll attempt to reproduce. In the mean time, the point of master and CA in the git repo (https://gerrit.iotivity.org/gerrit/p/iotivity.git ) are reasonably stable if you have access. On Fri, 2015-02-27 at 02

[dev] segmentation fault while running simpleclient

2015-02-26 Thread Keane, Erich
I don't see anything that is obvious on this one. Can you tell me what commit-id you are working off of? Perhaps I can see if I can reproduce it. Thanks! -Erich On Thu, 2015-02-26 at 19:10 +0800, Han-Lin Li wrote: > I run simpleclient and simpleserver by adb and get a segmentation fault > > >