Version: (using Devel) OS: OS X Installed from: Compiled sources 1. dsymutil=yes fails for binaries with spaces in their filenames; adding quotes fixes that. 2. dsymutil=yes runs multiple instances of dsymutil on same file if you happen to be valgrinding a multiprocess application; locking is needed to avoid this. Easy-ish workaround until those are fixed: run dsymutil manually.
Err, at least (1) is lame and easy to fix. Marking as blocking3.5.1.
Aw, #2 should be easy, too. I'll try to submit a patch for both later today.
Decided to go with the approach in bug 205000 instead, as manipulating dsym files turns out to be a can of worms (and running dsymutil for chromium takes 20 minutes on a 2.8GHz quad-core Xeon, probably much longer on our Mac Mini test bots, which is prohibitive).
Created attachment 49156 [details] Simply adds quotes around the path being passed to dsymutil. Here's a patch to add quotes around the path being passed to dsymutil.
Created attachment 49157 [details] Simply adds quotes around the path being passed to dsymutil. Here's a patch to add quotes around the path being passed to dsymutil.
Quoting fix committed as r11219 (thanks for that). The locking issue remains unresolved.