-
-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libprotobuf complains about invalid UTF-8 data #506
Comments
Hey @FaberFlorian , thanks for the report. This is an interesting problem. Could you run the build with |
Yes, of course I tried a rerun with --verbose (have a nice 1.5GB log file here :) and the problem did not appear. Seems to be a heisenbug :) |
I can try another set of runs in a few hours, for now I reverted to bear 2.x, it seems to work. |
Yes, bear 2.x does not use gRPC. This bug won't be there. Maybe some others. :) |
Hello, @rizsotto I encountered the same problem today. I tried to compile the kernel from android_kernel_hisi_hi3650. Bear has problem with this command Debug log:
Simplified steps to reproduce:
bear -- grep -obUaP $'\005\020\255\336' out/drivers/huawei_platform/oases/inlinehook_subfunc_post.bin
Bear version 3.0.18, installed via apt on Ubuntu 22.04. |
After having many more issues, I solved this by writing my own interceptor/CDB generator :) Side effect is no slowdown of the build. |
Describe the bug
The build aborts because non UTF-8-data seems to appear while building glibc-2.36.
To Reproduce
Cannot paste my full cross-compile environment here. It happens when building glibc-2.36:
-----------------------arm target--------------------------
The text was updated successfully, but these errors were encountered: