compile_command.json is empty

[SilverGreen93]

Describe the bug
After upgrading bear from 3.1.6 to 4.0.2, I get an empty compile_commands.json after running my build system with Bear:

bear -- build_all
[...]
❯ cat compile_commands.json
[]%

Running with 3.1.6 generates the compile_commands.json just fine.

Expected behavior
Version 4.0.2 should work the same as 3.1.6

Environment:

• OS name: Ubuntu
• OS version: 24.04
• OS architecture: x86_64
• Bear version: 4.0.2
• Bear install method: compiled from source following the instructions in INSTALL.md

Additional context

• My project is using gcc 11.4.0
• My build with Bear 3.1.6 takes about 2h to complete, but with Bear 4.0.2 seems it takes only 50min (the same time as if it was run without Bear), which might indicate that Bear does not do anything as it should.

[...]
[2026-01-19T10:45:20Z DEBUG bear::semantic::interpreters::combinators] coreutils_to_ignore : None
[2026-01-19T10:45:20Z DEBUG bear::intercept::supervise] Child process exited: ExitStatus(unix_wait_status(0))
[2026-01-19T10:45:20Z INFO  bear::output] Output pipeline:
      semantic events: 0
      current entries: 0
      previous entries: 0
      filtered entries by duplicate: 0
      filtered entries by source: 0
      total entries written: 0
[2026-01-19T10:45:20Z DEBUG bear] Exit code: ExitCode(unix_exit_status(0))

Let me know if I can share any more useful logs or what lines to look for in the debug log.

[rizsotto]

Thanks for the report... the runtime difference is not good indicator, since the 3.1 and 4.0 works differently.

Yes, it would be good to see some more logs in order to have some understanding about the issue. I presume the full log is very big, but some fragments would be good to see.

• the first 50 lines of the log to see how Bear starts up... what the arguments are, what the context is, what the config look like
• and maybe 200 more lines when some compilation happens... the preload library is loaded, the execution is intercepted, the recognition phase

And if you could share some details about this project.... is it using cross compiler? what is the path to the compiler we are expect to see (maybe 2 entries from the compile_commands.json file that was generated with the 3.1.6 version)?

[SilverGreen93]

Here is an example entry (abridged) from the compile_commands.json as generated by bear 3.1.6:

  {
    "arguments": [
      "/localdisk/yocto/x86_64/i686-sdk/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc",
      "-m64",
      "-fstack-protector-all",
      "-O2",
      "-Wformat",
      "-Werror",
      "-I/localdisk/sources/h",
      "-c",
      "-o",
      "/localdisk/sources/bld/test.o",
      "/localdisk/sources/test.c"
    ],
    "directory": "/localdisk/sources",
    "file": "/localdisk/sources/test.c",
    "output": "/localdisk/sources/bld/test.o"
  },

The bear 4.0.2 debug log does not have any debug messages other than the first 50 lines and the last 10:

[2026-01-19T11:42:17Z INFO  bear] bear v4.0.2
[2026-01-19T11:42:17Z INFO  bear] Running on... unix/linux x86_64
[2026-01-19T11:42:17Z INFO  bear] Application Context:
    Current Executable: /usr/local/bin/bear
    Current Directory: /localdisk/sources
    Preload Supported: true
    Total Environment Variables: 72 entries
    Relevant Environment Variables:
      PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/mihai/.fzf/bin
    
[2026-01-19T11:42:17Z INFO  bear] Arguments:
    Configuration File: <default>
    Mode: Combined (Intercept + Semantic Analysis)
      Input: Build Command: build_all
      Output: Semantic Output: compile_commands.json (append: false)
[2026-01-19T11:42:17Z DEBUG bear::config::loader] Checking configuration file: /localdisk/sources/bear.yml
[2026-01-19T11:42:17Z DEBUG bear::config::loader] Checking configuration file: /home/mihai/.config/bear.yml
[2026-01-19T11:42:17Z DEBUG bear::config::loader] Checking configuration file: /home/mihai/.config/bear/bear.yml
[2026-01-19T11:42:17Z DEBUG bear::config::loader] Configuration file not found. Using the default configuration.
[2026-01-19T11:42:17Z INFO  bear] Configuration:
    schema: '4.0'
    intercept:
      mode: preload
      path: /usr/local/libexec/bear/$LIB/libexec.so
    compilers: []
    sources:
      only_existing_files: true
    duplicates:
      match_on:
      - file
      - arguments
    format:
      paths:
        directory: as-is
        file: as-is
      entries:
        use_array_format: true
        include_output_field: true
    
[2026-01-19T11:42:17Z DEBUG bear::modes] Mode: intercept build and semantic analysis
[2026-01-19T11:42:17Z DEBUG bear] Configuration complete, running the build now...
[2026-01-19T11:42:17Z INFO  bear::intercept::environment] Build command to run: BuildCommand { arguments: ["build_all"] }
[2026-01-19T11:42:17Z INFO  bear::intercept::environment] Build command environment override: LD_PRELOAD=/usr/local/libexec/bear/$LIB/libexec.so
[2026-01-19T11:42:17Z INFO  bear::intercept::environment] Build command environment override: INTERCEPT_COLLECTOR_ADDRESS=127.0.0.1:42731
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] Recognizing execution: Execution { executable: "build_all", arguments: [], working_dir: "/localdisk/sources", environment: {"PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/mihai/.fzf/bin"} }
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] coreutils_to_ignore : None
[2026-01-19T11:42:17Z preload/828364] Initializing intercept-preload library
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] Recognizing execution: Execution { executable: "/usr/bin/perl", arguments: ["/usr/bin/perl", "/localdisk/sources/build.pl", "all"], working_dir: "/localdisk/sources", environment: {"LD_PRELOAD": "/usr/local/libexec/bear/$LIB/libexec.so", "INTERCEPT_COLLECTOR_ADDRESS": "127.0.0.1:42731", "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/mihai/.fzf/bin"} }
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] coreutils_to_ignore : None
[2026-01-19T11:42:17Z preload/828366] Initializing intercept-preload library
[...]
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] Recognizing execution: Execution { executable: "/bin/sh", arguments: ["sh", "-c", "build -j16 all"], working_dir: "/localdisk/sources", environment: {"PATH": "/bin:/usr/bin", "LD_PRELOAD": "/usr/local/libexec/bear/$LIB/libexec.so"} }
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] coreutils_to_ignore : None

After this point, the actual compilation starts, but there are no more bear logs until the end (which I pasted in the previous message).

The bear 3.1.6 debug log includes a lot more debugging lines and shows the debug lines capturing the gcc compile lines that produce the compile_commands.json above:

[14:29:37.752308, wr, 1218071, ppid: 1197553] wrapper: 3.1.6
[14:29:37.752349, wr, 1218071, ppid: 1197553] arguments: ["/usr/local/lib/x86_64-linux-gnu/bear/wrapper", "--destination", "dns:///localhost:36733", "--verbose", "--execute", "/bin/bash", "--", "/bin/bash", "-c", "echo \"[C  ] Compiling /localdisk/sources/test.c\""]
[14:29:37.753048, wr, 1218071, ppid: 1197553] environment: [...]
[14:29:37.753116, wr, 1218071, ppid: 1197553] arguments parsed: {program: /usr/local/lib/x86_64-linux-gnu/bear/wrapper, arguments: [{--: [/bin/bash, -c, echo "[C  ] Compiling /localdisk/sources/test.c"]}, {--destination: [dns:///localhost:36733]}, {--execute: [/bin/bash]}, {--verbose: []}]}
[14:29:37.765154, br, 890445] trying to resolve for library: /bin/bash
[14:29:37.754713, wr, 1218071, ppid: 1197553] gRPC call requested: supervise::Supervisor::Resolve
[14:29:37.766135, wr, 1218071, ppid: 1197553] gRPC call [Resolve] finished: true
[14:29:37.767129, wr, 1218071, ppid: 1197553] Process spawned. [pid: 1218078, command: ["/bin/bash", "-c", "echo \"[C  ] Compiling /localdisk/sources/test.c\""]]
[14:29:37.767272, wr, 1218071, ppid: 1197553] gRPC call requested: supervise::Interceptor::Register
[14:29:37.770202, el, 1218078] lib.cc; on_load
[C  ] Compiling /localdisk/sources/test.c
[14:29:37.771561, el, 1218078] lib.cc; on_unload
[14:29:37.772757, wr, 1218071, ppid: 1197553] gRPC call [Register] finished: true
[14:29:37.772910, wr, 1218071, ppid: 1197553] Process wait requested. [pid: 1218078]
[14:29:37.772925, wr, 1218071, ppid: 1197553] Process wait request: done. [pid: 1218078]
[14:29:37.772930, wr, 1218071, ppid: 1197553] gRPC call requested: supervise::Interceptor::Register
[14:29:37.773567, wr, 1218071, ppid: 1197553] gRPC call [Register] finished: true
[14:29:37.773933, wr, 1218071, ppid: 1197553] succeeded with: 0
[14:29:37.773999, el, 1218071] lib.cc; on_unload
cd /localdisk/sources && x86_64-poky-linux-gcc -m64 -fstack-protector-all -O2 -Wformat -Werror -O2 -I/localdisk/sources/h -c -o /localdisk/sources/bld/test.o /localdisk/sources/test.c
[14:29:37.775381, el, 1218079] lib.cc; execvp file: /bin/bash
[14:29:37.779300, el, 1218079] lib.cc; on_load
[14:29:37.780294, wr, 1218079, ppid: 1197553] wrapper: 3.1.6
[14:29:37.780547, wr, 1218079, ppid: 1197553] arguments: ["/usr/local/lib/x86_64-linux-gnu/bear/wrapper", "--destination", "dns:///localhost:36733", "--verbose", "--execute", "/bin/bash", "--", "/bin/bash", "-c", "cd /localdisk/sources && x86_64-poky-linux-gcc -m64 -fstack-protector-all -O2 -Wformat -Werror -O2 -I/localdisk/sources/h -c -o /localdisk/sources/bld/test.o /localdisk/sources/test.c"]
[14:29:37.781246, wr, 1218079, ppid: 1197553] environment: [...]
[14:29:37.781297, wr, 1218079, ppid: 1197553] arguments parsed: {program: /usr/local/lib/x86_64-linux-gnu/bear/wrapper, arguments: [{--: [/bin/bash, -c, cd /localdisk/sources && x86_64-poky-linux-gcc -m64 -fstack-protector-all -O2 -Wformat -Werror -O2 -I/localdisk/sources/h -c -o /localdisk/sources/bld/test.o /localdisk/sources/test.c]}, {--destination: [dns:///localhost:36733]}, {--execute: [/bin/bash]}, {--verbose: []}]}
[14:29:37.791741, br, 890445] trying to resolve for library: /bin/bash
[14:29:37.782885, wr, 1218079, ppid: 1197553] gRPC call requested: supervise::Supervisor::Resolve
[14:29:37.792750, wr, 1218079, ppid: 1197553] gRPC call [Resolve] finished: true
[14:29:37.793842, wr, 1218079, ppid: 1197553] Process spawned. [pid: 1218086, command: ["/bin/bash", "-c", "cd /localdisk/sources && x86_64-poky-linux-gcc -m64 -fstack-protector-all -O2 -Wformat -Werror -O2 -I/localdisk/sources/h -c -o /localdisk/sources/bld/test.o /localdisk/sources/test.c"]]
[14:29:37.793990, wr, 1218079, ppid: 1197553] gRPC call requested: supervise::Interceptor::Register
[14:29:37.796756, el, 1218086] lib.cc; on_load
[14:29:37.798792, el, 1218086] lib.cc; execve path: /localdisk/yocto/x86_64/i686-sdk/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc
[14:29:37.801317, wr, 1218079, ppid: 1197553] gRPC call [Register] finished: true
[14:29:37.801507, wr, 1218079, ppid: 1197553] Process wait requested. [pid: 1218086]
[14:29:37.803019, el, 1218086] lib.cc; on_load

[rizsotto]

Thanks for the update. Is the GCC a static binary? Or the shell it executes the compiler call? Or the perl that orchestrates the build?

[SilverGreen93]

Thanks for the update. Is the GCC a static binary? Or the shell it executes the compiler call? Or the perl that orchestrates the build?

Hope it helps:

For gcc:

❯ file `which x86_64-poky-linux-gcc`
/localdisk/yocto/x86_64/sysroots/x86_64-pokysdk-linux/usr/bin/x86_64-poky-linux/x86_64-poky-linux-gcc: ELF 64-bit LSB executable, x86-64, version 1 (GNU/Linux), dynamically linked, interpreter /localdisk/yocto/x86_64/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2, BuildID[sha1]=219f87863a7eef5ab5f985d355535338eda40585, for GNU/Linux 3.2.0, stripped

❯ ldd `which x86_64-poky-linux-gcc`
        linux-vdso.so.1 (0x00007fffc0bcb000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff196f52000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff196c00000)
        /localdisk/yocto/x86_64/sysroots/x86_64-pokysdk-linux/lib/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x00007ff197051000)

For sh:

❯ file `which sh`  
/usr/bin/sh: symbolic link to /bin/bash

❯ file /bin/bash  
/bin/bash: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=2f77b36371c214e11670c7d9d92727e9a49f626b, for GNU/Linux 3.2.0, stripped

❯ ldd /bin/bash
        linux-vdso.so.1 (0x00007ffc7b181000)
        libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007007339af000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x0000700733600000)
        /lib64/ld-linux-x86-64.so.2 (0x0000700733b65000)

For perl (the perl that appears in the bear 3.1.6 logs):

❯ file /usr/bin/perl    
/usr/bin/perl: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=7d451f1287f781b8400262dfc337b9dd41d118fb, for GNU/Linux 3.2.0, stripped

❯ ldd /usr/bin/perl
        linux-vdso.so.1 (0x00007ffe14b8f000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x000077ecd9aa0000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x000077ecd9200000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x000077ecd9a66000)
        /lib64/ld-linux-x86-64.so.2 (0x000077ecd9b9f000)

but:

❯ ldd `which perl`                 
        not a dynamic executable

❯ file `which perl`                 
/localdisk/yocto/x86_64/sysroots/x86_64-pokysdk-linux/usr/bin/perl: Bourne-Again shell script, ASCII text executable

[rizsotto]

Interesting... So you are saying that the debug log only contains the perl "recognizing execution", no compiler calls with this message?

[SilverGreen93]

If you are referring to Bear 4.0.2 logs, yes, there are no logs with compiler calls and "recognizing execution", as they are in bear 3.1.6.

Here is a snippet from Bear 3.1.6 debug logs related to perl calls:

[14:29:01.105400, br, 890445] trying to resolve for library: /usr/bin/perl
[14:29:01.104388, el, 1197163] lib.cc; on_unload
[14:29:01.105611, el, 1197178] lib.cc; execvp file: perl
[14:29:01.105903, wr, 1197167, ppid: 1196811] gRPC call [Resolve] finished: true
[14:29:01.106595, wr, 1197167, ppid: 1196811] Process spawned. [pid: 1197179, command: ["perl", "-e", "($t,$n)=@ARGV;unlink($n);-e $n&&exit(0);use Cwd qw(abs_path);$n=~m,^(/.*)/,||die \"bad path: $n\\n\";@n=split(\"/\",(-d \"$1/.\"?abs_path($1):$1));@t=split(\"/\",$t);while(@n&&@t&&$n[0]eq$t[0]){shift @n;shift @t;}$l=join(\"/\",(map{\"..\"}@n),@t);symlink($l,$n)||die \"symlink($l,$n): $!\\n\";", "/localdisk/sources/bld/_common", "/localdisk/sources/objdir/_common"]]
[14:29:01.106660, wr, 1197167, ppid: 1196811] gRPC call requested: supervise::Interceptor::Register
[14:29:01.109500, el, 1197178] lib.cc; on_load
[14:29:01.109664, el, 1197179] lib.cc; on_load
[14:29:01.110526, wr, 1197178, ppid: 1196857] wrapper: 3.1.6
[14:29:01.110604, wr, 1197178, ppid: 1196857] arguments: ["/usr/local/lib/x86_64-linux-gnu/bear/wrapper", "--destination", "dns:///localhost:36733", "--verbose", "--execute", "/usr/bin/perl", "--", "perl", "-e", "($t,$n)=@ARGV;unlink($n);-e $n&&exit(0);use Cwd qw(abs_path);$n=~m,^(/.*)/,||die \"bad path: $n\\n\";@n=split(\"/\",(-d \"$1/.\"?abs_path($1):$1));@t=split(\"/\",$t);while(@n&&@t&&$n[0]eq$t[0]){shift @n;shift @t;}$l=join(\"/\",(map{\"..\"}@n),@t);symlink($l,$n)||die \"symlink($l,$n): $!\\n\";", "/localdisk/sources/bld/_a64", "/localdisk/sources/objdir/_a64"]
[14:29:01.110791, wr, 1197178, ppid: 1196857] environment: ["GNUMAKE=make", "INTERCEPT_REPORT_COMMAND=/usr/local/lib/x86_64-linux-gnu/bear/wrapper", "INTERCEPT_REPORT_DESTINATION=dns:///localhost:36733", "INTERCEPT_VERBOSE=true", "LANG=C", "LD_PRELOAD=/usr/local/lib/x86_64-linux-gnu/bear/libexec.so", "PWD=/localdisk/sources", ... ]
[14:29:01.110824, wr, 1197178, ppid: 1196857] arguments parsed: {program: /usr/local/lib/x86_64-linux-gnu/bear/wrapper, arguments: [{--: [perl, -e, ($t,$n)=@ARGV;unlink($n);-e $n&&exit(0);use Cwd qw(abs_path);$n=~m,^(/.*)/,||die "bad path: $n\n";@n=split("/",(-d "$1/."?abs_path($1):$1));@t=split("/",$t);while(@n&&@t&&$n[0]eq$t[0]){shift @n;shift @t;}$l=join("/",(map{".."}@n),@t);symlink($l,$n)||die "symlink($l,$n): $!\n";, /localdisk/sources/bld/_a64, /localdisk/sources/objdir/_a64]}, {--destination: [dns:///localhost:36733]}, {--execute: [/usr/bin/perl]}, {--verbose: []}]}
[14:29:01.112272, wr, 1197178, ppid: 1196857] gRPC call requested: supervise::Supervisor::Resolve
[14:29:01.113077, wr, 1197167, ppid: 1196811] gRPC call [Register] finished: true
[14:29:01.119327, br, 890445] trying to resolve for library: /usr/bin/perl
[14:29:01.113196, wr, 1197167, ppid: 1196811] Process wait requested. [pid: 1197179]
[14:29:01.119838, wr, 1197178, ppid: 1196857] gRPC call [Resolve] finished: true
[14:29:01.120449, wr, 1197178, ppid: 1196857] Process spawned. [pid: 1197186, command: ["perl", "-e", "($t,$n)=@ARGV;unlink($n);-e $n&&exit(0);use Cwd qw(abs_path);$n=~m,^(/.*)/,||die \"bad path: $n\\n\";@n=split(\"/\",(-d \"$1/.\"?abs_path($1):$1));@t=split(\"/\",$t);while(@n&&@t&&$n[0]eq$t[0]){shift @n;shift @t;}$l=join(\"/\",(map{\"..\"}@n),@t);symlink($l,$n)||die \"symlink($l,$n): $!\\n\";", "/localdisk/sources/bld/_a64", "/localdisk/sources/objdir/_a64"]]
[14:29:01.120513, wr, 1197178, ppid: 1196857] gRPC call requested: supervise::Interceptor::Register
[14:29:01.121475, el, 1197179] lib.cc; on_unload

This is the only line related to perl in Bear 4.0.2 logs:

[2026-01-19T11:42:17Z preload/828364] Initializing intercept-preload library
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] Recognizing execution: Execution { executable: "/usr/bin/perl", arguments: ["/usr/bin/perl", "/localdisk/sources/build.pl", "all"], working_dir: "/localdisk/sources", environment: {"LD_PRELOAD": "/usr/local/libexec/bear/$LIB/libexec.so", "INTERCEPT_COLLECTOR_ADDRESS": "127.0.0.1:42731", "PATH": "/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin:/home/mihai/.fzf/bin"} }
[2026-01-19T11:42:17Z DEBUG bear::semantic::interpreters::combinators] coreutils_to_ignore : None

Seems that the gcc lines are not captured at all by Bear 4.0.2

[rizsotto]

Thanks for confirming it. Looks like the intercept does not work with your build. Is it possible that the build reset the environment variables? I have a theory why this was not an issue with the previous version. But to see the build system would help me to better understand. Is this project open source?

I know that you have a workaround (to use the previous version), but do you want to test if the wrapper mode works with your build? The man page describes how the config file should look like to run it that way.

[SilverGreen93]

Thanks for confirming it. Looks like the intercept does not work with your build. Is it possible that the build reset the environment variables?

I'm pretty sure the build helper (the perl script) starts a lot of sub-shells and I don't know if it resets them, but definitely modifies them.

But to see the build system would help me to better understand. Is this project open source?

Unfortunately no, it's not open-source. It's quite an old (90s-2000s) clearmake project which I upgraded to a newer gcc and standard make by dynamically converting the original makefiles to standard makefiles with helper translation scripts, then the build is orchestrated by perl scripts somehow, but I don't quite have myself the whole picture on its inner workings to help explain it to you better. I was happy enough that Bear 3.1.6 can intercept the commands to make sense of the project by using the compile_commands.json.

I know that you have a workaround (to use the previous version), but do you want to test if the wrapper mode works with your build? The man page describes how the config file should look like to run it that way.

I need to read more about this mode and see how I can make it work.

I have a theory why this was not an issue with the previous version.

I would be happy to test any hunch you might have to make this project better ;)

Edit: I see these lines in the 3.1.6 debug info:

[14:29:37.780294, wr, 1218079, ppid: 1197553] wrapper: 3.1.6

Does this mean that 3.1.6 is ran in wrapper mode by default and 4.0.2 in intercept?

[rizsotto]

The 3.x version was working differently. The preload mode was executing a wrapper (that's the log about) and the wrapper was executing the compiler. This would enable to derive metrics about a project, like module compilation time. But that was not developed, and the wrappers might cause issues for some build environments. So in the new version preload reports the execution and calls the compiler. It also works with compiler wrappers, which can be enabled through config file.

I'm traveling at the moment with my phone only, will be back next month, when I can improve the preload module. Will ping you here if you don't mind.

[SilverGreen93]

Is it possible that the build reset the environment variables?

I think I found the place that resets the environment variables in my build system. Can you tell me which bear-related variables should I keep an eye on? I presume INTERCEPT_COLLECTOR_ADDRESS and LD_PRELOAD should do.

[rizsotto]

Correct. Those would be enough to make it work... I will make sure that Bear will insert those when calling the exec functions. But in the current state if the build system does not remove them that's a good fix too.

[rizsotto]

I have made a fix for this issue. Could you test it against your project? It's on 4.0.3-rc branch.

[SilverGreen93]

I have made a fix for this issue. Could you test it against your project? It's on 4.0.3-rc branch.

Thanks for trying, but it seems there is no change, the result is still empty.
I also tried keeping INTERCEPT_COLLECTOR_ADDRESS and LD_PRELOAD variables on env reset, but still no success.