-
Notifications
You must be signed in to change notification settings - Fork 13.3k
dsymutil hang when compiling Servo without optimization #15978
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
Comments
Here is a dsymutil backtrace when it's hung: |
cc @michaelwoerister just in case |
If I rerun I don't understand why the backtrace (both there with LLDB and locally when I use |
It does appear that dsymutil is writing its large number of warnings about invalid DWARF to stdout rather than stderr, though. Perhaps rustc is doing something to cause the flush to block on the other side? |
If rustc has redirected dsymutil to a pipe and doesn't read from it while the process is running, dsymutil will hang when the pipe's buffer fills up. |
I think this patch should fix it, but building a local |
That patch fixes it, but I can't actually run the resulting servo binary because it doesn't find the dylibs. Is there some standard way of getting the correct |
If you compile with |
I filed a specific issue for the problem here: #16060. |
This seems to be fixed now, yeah? |
Sounds like it. |
Compiling https://github.com/servo/servo/tree/rustup-20140716 works fine on OS X, but if you add
--disable-optimize
on configure, then the build will hang in libscript. Inspecting rustc in a debugger shows that it's waiting on an external process; the process appears to be dsymutil since that is still running.@alexcrichton suspects it's a debuginfo related bug.
The text was updated successfully, but these errors were encountered: