Note the "rep = null" value. I would expect that to be "1". I know I must be missing something. It seems that I can only pull one value at a time, but not two. Thanks in advance from a new json-c user :)
> Note the "rep = null" value. I would expect that to be "1". I know I must > be missing something. It seems that I can only pull one value at a time, > but not two. Thanks in advance from a new json-c user :)
On Monday, April 30, 2012 7:20:05 PM UTC-4, Da Beave wrote:
> I have the following type of json input coming from a webserver:
> Note the "rep = null" value. I would expect that to be "1". I know I must > be missing something. It seems that I can only pull one value at a time, > but not two. Thanks in advance from a new json-c user :)
On Monday, April 30, 2012 7:20:05 PM UTC-4, Da Beave wrote:
> I have the following type of json input coming from a webserver:
> Note the "rep = null" value. I would expect that to be "1". I know I must > be missing something. It seems that I can only pull one value at a time, > but not two. Thanks in advance from a new json-c user :)
Right here you lost the reference to your original object. You need
another struct json_object variable so you can work with the things you
pull out of the one you got from json_tokener_parse().
> Right here you lost the reference to your original object. You need > another struct json_object variable so you can work with the things you > pull out of the one you got from json_tokener_parse().
My question is whether I need decrease the reference
obj_1(json_object_put(obj_1)) before return the function, and obj_2?
If I use json_object_put(obj_1) in a sub function,I get a error,"***
glibc detected *** double free or corruption (!prev)".
On 5月1日, 上午9时37分, Eric Haszlakiewicz <haw...@gmail.com> wrote:
> Right here you lost the reference to your original object. You need
> another struct json_object variable so you can work with the things you
> pull out of the one you got from json_tokener_parse().
On Sat, Jun 16, 2012 at 1:54 AM, vistamin <feiyangena...@gmail.com> wrote:
> Hi, Eric.I don't know the following function whether is right or
> not.My english is poor,sorry.
> {
> struct json_object *obj_1;
> struct json_object *obj_2;
> My question is whether I need decrease the reference
> obj_1(json_object_put(obj_1)) before return the function, and obj_2?
> If I use json_object_put(obj_1) in a sub function,I get a error,"***
> glibc detected *** double free or corruption (!prev)".
You don't need to call json_object_put on obj_2 because
json_object_object_get() doesn't increment the reference count. That means
that because obj_2 is still part of obj_1 it will be automatically freed
when obj_1 is freed by the json_object_put(obj_1) call.
If you want to work with obj_2 separately (e.g. perhaps you want to have a
function that returns just that object, and not the surrounding obj_1), you
would need to explicitly increase the reference count with
json_object_get(obj_2) and *only* in that case would you need to call
json_object_put(obj_2).
Hi,Eric.Thank you for your quick reply.
I upload a attachment and show how I use json-c lib in my project, not only parsing a configuration file(json format) but also encoding/decoding message in a private protocol.
The error "***glibc detected *** double free or corruption (!prev)" puzzle me a long time, So I want to know whether I made a mistake when I use some functions in the json-lib.
> On Sat, Jun 16, 2012 at 1:54 AM, vistamin <feiyangena...@gmail.com> wrote:
>> Hi, Eric.I don't know the following function whether is right or
>> not.My english is poor,sorry.
>> {
>> struct json_object *obj_1;
>> struct json_object *obj_2;
>> My question is whether I need decrease the reference
>> obj_1(json_object_put(obj_1)) before return the function, and obj_2?
>> If I use json_object_put(obj_1) in a sub function,I get a error,"***
>> glibc detected *** double free or corruption (!prev)".
> You don't need to call json_object_put on obj_2 because > json_object_object_get() doesn't increment the reference count. That means > that because obj_2 is still part of obj_1 it will be automatically freed > when obj_1 is freed by the json_object_put(obj_1) call.
> If you want to work with obj_2 separately (e.g. perhaps you want to have a > function that returns just that object, and not the surrounding obj_1), you > would need to explicitly increase the reference count with > json_object_get(obj_2) and *only* in that case would you need to call > json_object_put(obj_2).
On Jun 16, 2012 9:31 PM, "vistamin" <feiyangena...@gmail.com> wrote:
> Hi,Eric.Thank you for your quick reply.
> I upload a attachment and show how I use json-c lib in my project, not
only parsing a configuration file(json format) but also encoding/decoding
message in a private protocol.
> The error "***glibc detected *** double free or corruption (!prev)"
puzzle me a long time, So I want to know whether I made a mistake when I
use some functions in the json-lib.
Well, since you commented out the extra json_object_put() calls it looks
like it should work. I would recommend trimming down you code to a smaller
test case to see if you can narrow down when the error happens.
> On Jun 16, 2012 9:31 PM, "vistamin" <feiyangena...@gmail.com> wrote:
> > Hi,Eric.Thank you for your quick reply.
> > I upload a attachment and show how I use json-c lib in my project, not > only parsing a configuration file(json format) but also encoding/decoding > message in a private protocol.
> > The error "***glibc detected *** double free or corruption (!prev)" > puzzle me a long time, So I want to know whether I made a mistake when I > use some functions in the json-lib.
> Well, since you commented out the extra json_object_put() calls it looks > like it should work. I would recommend trimming down you code to a smaller > test case to see if you can narrow down when the error happens.
I test the memory usage when I use json_object_put function on obj_1 or obj_2. Because I use json_token_parse() function, json_object_object_get() and json_object_put() functions in a sub function, So I can check memory usage easily.
By the way, I use "top" command to see the memory usage.
1. If I use json_object_put(obj_1) and comment json_object_put(obj_2),there is a memory leak.The memory usage changes from 11% to 24%.When the progarm exit, there is a error "*** glibc detected *** double free or corruption (!prev)"
2. If I use json_object_put(obj_2) and comment json_object_put(obj_1),there is a memory leak.The memory usage changes from 11% to 27%.When the progarm exit, there is a error "*** glibc detected *** double free or corruption (!prev)"
3. If I use json_object_put(obj_1) and use json_object_put(obj_2), the memory usage changes from 11% to 13%.When the progarm exit, there is a error "*** glibc detected *** double free or corruption (!prev)"
4. If I comment json_object_put(obj_1) and comment json_object_put(obj_2),there is a memory leak.The memory usage changes from 11% to 30%.The Error doesn't appear.How strange!
> On Sat, Jun 16, 2012 at 1:54 AM, vistamin <feiyangena...@gmail.com> wrote:
>> Hi, Eric.I don't know the following function whether is right or
>> not.My english is poor,sorry.
>> {
>> struct json_object *obj_1;
>> struct json_object *obj_2;
>> My question is whether I need decrease the reference
>> obj_1(json_object_put(obj_1)) before return the function, and obj_2?
>> If I use json_object_put(obj_1) in a sub function,I get a error,"***
>> glibc detected *** double free or corruption (!prev)".
> You don't need to call json_object_put on obj_2 because > json_object_object_get() doesn't increment the reference count. That means > that because obj_2 is still part of obj_1 it will be automatically freed > when obj_1 is freed by the json_object_put(obj_1) call.
> If you want to work with obj_2 separately (e.g. perhaps you want to have a > function that returns just that object, and not the surrounding obj_1), you > would need to explicitly increase the reference count with > json_object_get(obj_2) and *only* in that case would you need to call > json_object_put(obj_2).
Sorry ,this is no memory leak when I use json_object_put(obj_1) and not json_object_put(obj_2),I made a statistic mistake. But the "double free ..."error still appear.
> I test the memory usage when I use json_object_put function on obj_1 or > obj_2. > Because I use json_token_parse() function, json_object_object_get() and > json_object_put() functions in a sub function, So I can check memory usage > easily.
> By the way, I use "top" command to see the memory usage.
> 1. If I use json_object_put(obj_1) and comment > json_object_put(obj_2),there is a memory leak.The memory usage changes from > 11% to 24%.When the progarm exit, there is a error "*** glibc detected *** > double free or corruption (!prev)"
> 2. If I use json_object_put(obj_2) and comment > json_object_put(obj_1),there is a memory leak.The memory usage changes from > 11% to 27%.When the progarm exit, there is a error "*** glibc detected *** > double free or corruption (!prev)"
> 3. If I use json_object_put(obj_1) and use json_object_put(obj_2), the > memory usage changes from 11% to 13%.When the progarm exit, there is a > error "*** glibc detected *** double free or corruption (!prev)"
> 4. If I comment json_object_put(obj_1) and comment > json_object_put(obj_2),there is a memory leak.The memory usage changes from > 11% to 30%.The Error doesn't appear.How strange!
> I don't konw why.
> 在 2012年6月16日星期六UTC+8下午11时06分12秒，Eric写道：
>> On Sat, Jun 16, 2012 at 1:54 AM, vistamin <feiyangena...@gmail.com>wrote:
>>> Hi, Eric.I don't know the following function whether is right or
>>> not.My english is poor,sorry.
>>> {
>>> struct json_object *obj_1;
>>> struct json_object *obj_2;
>>> My question is whether I need decrease the reference
>>> obj_1(json_object_put(obj_1)) before return the function, and obj_2?
>>> If I use json_object_put(obj_1) in a sub function,I get a error,"***
>>> glibc detected *** double free or corruption (!prev)".
>> You don't need to call json_object_put on obj_2 because >> json_object_object_get() doesn't increment the reference count. That means >> that because obj_2 is still part of obj_1 it will be automatically freed >> when obj_1 is freed by the json_object_put(obj_1) call.
>> If you want to work with obj_2 separately (e.g. perhaps you want to have >> a function that returns just that object, and not the surrounding obj_1), >> you would need to explicitly increase the reference count with >> json_object_get(obj_2) and *only* in that case would you need to call >> json_object_put(obj_2).
On Jun 18, 2012 5:58 AM, "vistamin" <feiyangena...@gmail.com> wrote:
> Sorry ,this is no memory leak when I use json_object_put(obj_1) and not
json_object_put(obj_2),I made a statistic mistake.
> But the "double free ..."error still appear.
If you're running this on linux I would recommend using valgrind to try to
track down where the problem is coming from. If you pass it the
--track-origins=yes option it should tell you not only where the second,
invalid free call happened but also where the memory was first freed.
That should help you determine whether you're doing something wrong, such
as calling json_object_put too many times, or whether json-c has a bug.
If it's a bug in json-c and you can put together a *small* test case, I
will take a look at fixing it.
