3.6/f/json parser unit test

[bazsi]

No description provided.

[algernon]

There's still a segmentation fault in the test case. I see it on Travis, but have not tried it locally yet.

[algernon]

I think test_json_parser_validate_type_representation() is failing, as that's the only test that contains a NULL value, which is mentioned in the error message:

[2014-01-02T14:11:06.194677] Unparsable JSON stream encountered; error='null expected'
/bin/bash: line 5:  3474 Segmentation fault      ${dir}$tst
FAIL: modules/json/tests/test_jsonparser

I suspect this may have to do something with Travis having json-c 0.9, while I have 0.11 locally. I'll try to reproduce it on a Precise chroot.

[bazsi]

I have updated a branch now with the following changes:

1. the segfault should be gone, I compiled an old json-c locally and the root cause was that json-c 0.9 actually stores a NULL value instead of a null json object. Handling the NULL makes the segfault go away for me.

2. it contains a couple of follow-up changes that the unit test permitted me to make. Instead of adding those to the nodejs-support branch, which I'm submitting for merging in just a minute.

[algernon]

Nice catch with json-c! I skimmed through the patches, and they all look good. Fingers crossed for Travis thinking similarly.