commit | ae95864b6b338f04ab25e389824a632087f1bd60 | [log] [tgz] |
---|---|---|
author | Emanuele Torre <torreemanuele6@gmail.com> | Tue Jul 25 20:50:45 2023 +0200 |
committer | Nico Williams <nico@cryptonector.com> | Tue Jul 25 14:51:58 2023 -0500 |
tree | 162fb004d54cc896f80a6cc331faa166f64c28f9 | |
parent | a949745059ee61366a5d880c3b18d5d4db6524eb [diff] |
Make sure to free default `@text` format on error It seems that bison doesn't call destructors for mid-rule action components on error, since it does not know their type. A mid-rule action was used to allocate the "text" string used as format by string literals without a format, which would leak on error. This patch replaces it with a new NoFormat component of type <literal>. Now bison will call jv_free() on that string after a syntax error. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=60836 $ ./jq '"' jq: error: syntax error, unexpected end of file, expecting QQSTRING_TEXT or QQSTRING_INTERP_START or QQSTRING_END (Unix shell quoting issues?) at <top-level>, line 1: " jq: 1 compile error ================================================================= ==1495450==ERROR: LeakSanitizer: detected memory leaks Direct leak of 21 byte(s) in 1 object(s) allocated from: #0 0x7fc21aee1359 in __interceptor_malloc /usr/src/debug/gcc/gcc/libsanitizer/asan/asan_malloc_linux.cpp:69 #1 0x557ccb6ff608 in jv_mem_alloc src/jv_alloc.c:141 SUMMARY: AddressSanitizer: 21 byte(s) leaked in 1 allocation(s).
jq is a lightweight and flexible command-line JSON processor.
If you want to learn to use jq, read the documentation at https://jqlang.github.io/jq. This documentation is generated from the docs/ folder of this repository. You can also try it online at jqplay.org.
If you want to hack on jq, feel free, but be warned that its internals are not well-documented at the moment. Bring a hard hat and a shovel. Also, read the wiki: https://github.com/jqlang/jq/wiki, where you will find cookbooks, discussion of advanced topics, internals, release engineering, and more.
Source tarball and built executable releases can be found on the homepage and on the github release page, https://github.com/jqlang/jq/releases. Docker image is available at https://github.com/jqlang/jq/pkgs/container/jq.
If you‘re building directly from the latest git, you’ll need libtool, make, automake, and autoconf installed. To get regexp support you'll also need to install Oniguruma or clone it as a git submodule as per the instructions below. To build, run:
git submodule update --init # if building from git to get oniguruma autoreconf -i # if building from git ./configure --with-oniguruma=builtin make -j8 make check
Developers must --enable-maintainer-mode
when making changes to the jq parser and lexer which also requires bison and flex to be installed.
To build a statically linked version of jq, run:
make LDFLAGS=-all-static
After make finishes, you'll be able to use ./jq
. You can also install it using:
sudo make install
If you‘re not using the latest git version but instead building a released tarball (available on the website), then you won’t need to run autoreconf
(and shouldn‘t), and you won’t need flex or bison.
To cross-compile for OS X and Windows, see docs/Rakefile‘s build task and scripts/crosscompile. You’ll need a cross-compilation environment, such as Mingw for cross-compiling for Windows.
Cross-compilation requires a clean workspace, then:
# git clean ... autoreconf -i ./configure make distclean scripts/crosscompile <name-of-build> <configure-options>
Use the --host=
and --target=
./configure options to select a cross-compilation environment. See also “Cross compilation” on the wiki.
To compile jq to WebAssembly, install the Emscripten SDK, then:
git submodule update --init # if building from git to get oniguruma autoreconf -i # if building from git emconfigure ./configure --with-oniguruma=builtin emmake make EXEEXT=.js CFLAGS="-O2" LDFLAGS="-s EXPORTED_RUNTIME_METHODS=['callMain']"