build gcc with error

[ywgrit]

Describe the bug
A clear and concise description of what the bug is.
I build the gcc from gnu with some code changed. Without bear, the build process succeed. With bear, it failed.

The command executed: numactl -N 6 -m 6 bear --verbose -- bash build.sh debug 2>&1 | tee build_log_error.json

build.sh

compile_commands.json

build_log_error.json

The build_log_error is only contains the failed information because the generated log is too big(500MB)

I tried numactl -N 6 -m 6 bear --verbose --force-wrapper -- bash build.sh debug the build process succeed but compile_commands.json is empty

To Reproduce

Expected behavior
Build process should be succeed and compile_commands.json should be correct.

Environment:

• OS name: linux
• OS version: Ubuntu 22.04 LTS x86_64
• OS architecture: x86_64
• Bear version: 3.1.3
• Bear install method: build from source

Additional context

• Can you give us a reference to the project that you are running against this tool? [e.g. No if it's a close source project, but in case of an open source project a link to the sources could be nice.]
• What build tools this project is using? [e.g. GNU make wtih configure script]
• What architecture you are trying to compile for? [e.g. cross compiling]
• Could you attach build logs? If you can re-run the command which failed (e.g. bear -- make) with extra verbose log switches (e.g. bear --verbose -- make) and send the output of it, that would help a lot.

Before you send...

• Have you read the README.md file or man bear?
  yes
• Have you looked what other open issues Bear has?
  There are similar issue, i.e., 498, but the problem has not been solved yet.
• Are you sure that the build works without Bear?
  yes.

[rizsotto]

What's the benefit to run with --force-wrapper?

The configure script will find the real compiler and will call it directly, skipping over the wrapper. So, there won't be way for Bear to capture the compile commands.

[ywgrit]

What's the benefit to run with --force-wrapper?

The configure script will find the real compiler and will call it directly, skipping over the wrapper. So, there won't be way for Bear to capture the compile commands.

Hi, I tried to run bear with '--force-wrapper' because without '--force-wrapper', the build process failed.
How could I run bear sucessfully with build.sh and make sure the compile_commands.json is generated correctly? The build_log_error.json record some failed things, but I can not understand it as it seems to be the error information for the source code of bear

[rizsotto]

I don't see any errors that would be fatal. (And might cause incomplete compilation database.)

Is the output usable? Or could you point out the build log line that you think is suspicious?