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
Bear is stuck #443
Comments
Hey Martin, I need more context in order to help. Could you fill out the issue template? Also, run the command with verbose flag and attach the output? Thanks! |
All right, so info from the issue template would be:
Bear is from openSUSE TW distribution, normally installed package. Using
|
Interesting log!!! I've seen the message Is that possible that the Is this a GCC build? This was problematic on Kali linux too. GCC is executes I don't really know how to fix empty |
So what's weird is that w/o the Plus I think GCC drive uses
|
And yes,
|
Nice catch, Bear reports |
I'm trying to reproduce it with the latest master, but the bug does not show up... The verbose log shows that it's using This is what I'm running on Fedora or Arch:
|
Not sure this is related, but I've never been able to do a parallel build of gcc with bear (same symptom as @marxin, build is stuck at the end). I usually do a sequential build when I'm not doing any dev. IIRC, @philberty had the same issue). |
@dkm there are two issues you mention:
|
I've seen Things to try our:
|
I have a similar problem; my problem arises whenever I use more than 6 jobs for make. |
I get the same issue at various gcc build steps when used with crosstool-ng, even with only one job. During the build, even the main Bear 2.4.4 works, and is a lot faster. |
FWIW, I've tried again this morning using a freshly built
The The process never seems to finish, I don't see any CPU activity, still have plenty of free RAM... So not sure what's wrong.:
|
+1, I'm facing the same issue with gccrs. If I use |
Thanks guys for this report. Is there a way that you could identify the command that hung the build? And create a minimal example which could help me to reproduce this error? That would be a great help to fix this bug. |
Sure, I'll see what I can find, thanks @rizsotto |
Is there a way to see what is being executed? I have a stuck |
Maybe try |
I've got a stuck bear, with the last lines on the term being:
The log is rather big with all my env, so not very comfortable putting it here. I can give it to someone for debuging :) The last command seems to be:
|
Thanks @dkm for this update. Will test if that command alone can cause the build stuck. But what I find strange is the output you've pasted here reports the whole build process was finished. The |
Oh, maybe some thread was started with incorrect parameter and is preventing the process to finish until it is joined? |
I can't build GCC with bear, where it's stack at the end of compilation:
There's process tree:
Where I'm using the latest release:
The text was updated successfully, but these errors were encountered: