ninja crashes with SIGSEGV (Address boundary error) due to broken .ninja-deps file |
|
Issue descriptionI just had an issue compiling chrome: > ninja -C out/Default/ -j2000 chrome fish: “ninja -C out/Default/ -j2000 ch…” terminated by signal SIGSEGV (Address boundary error) Without any further errors or stacktraces. Deleting .ninja-deps in out/Default fixed the issue for me but I have no idea, why the .ninja-deps file was corrupted. I'm using the ninja executable from depot_tools. Here is my faulty file: https://drive.google.com/drive/folders/0ByifqR9x_QRSV2Nzd3VkdzI0Qnc?usp=sharing (shared with @google.com, I'm not sure what exactly is inside this 100mb file) My gn args are the following: use_goma = true remove_webcore_debug_symbols = true is_component_build = true enable_nacl = false
,
Jun 1 2017
Linux, my ubuntu workstation.
,
Jun 22 2017
The .ninja_deps file stores header dependency information. `ninja -t deps` can dump its contents in a more readable format. It's mostly source filenames, so unless you're in a checkout with secret file names for some reason, you can share it more publicly. I can reproduce this with the ninja binary in depot_tools. I can't reproduce this in locally-built ninjas, either at trunk or the v1.7.2 tag. (I really should publish symbols with the release binaries somewhere.) I also tried building ninja locally with asan. |
|
►
Sign in to add a comment |
|
Comment 1 by thakis@chromium.org
, Jun 1 2017