Skip to content
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

Finding dSYM file on macOS can be very slow #11

Closed
bjorn3 opened this issue Apr 14, 2019 · 3 comments · Fixed by #12
Closed

Finding dSYM file on macOS can be very slow #11

bjorn3 opened this issue Apr 14, 2019 · 3 comments · Fixed by #12

Comments

@bjorn3
Copy link
Contributor

bjorn3 commented Apr 14, 2019

I have to run locate_debug_symbols in a spin loop, because it takes quite a time for spotlight to index it. I have even got >60s several times.

bjorn3 added a commit to bjorn3/pretty_backtrace that referenced this issue Apr 14, 2019
@bjorn3
Copy link
Contributor Author

bjorn3 commented Apr 14, 2019

bjorn3/pretty_backtrace@5be873a worked around this by adding a fast path for the case of the current executable being at target/<channel>/??? and the debuginfo being at target/<channel>/{deps,examples}. (Eg when using cargo run) It also adds a spin loop waiting for spotlight to find the debuginfo.

@bjorn3 bjorn3 mentioned this issue Apr 14, 2019
@luser
Copy link
Collaborator

luser commented Apr 15, 2019

We've got code to do simple path manipulation to support locating dSYM files on non-macOS systems, maybe we should try that first even on macOS, and only fall back to using Spotlight if that doesn't work?

@bjorn3
Copy link
Contributor Author

bjorn3 commented Apr 15, 2019

We've got code to do simple path manipulation to support locating dSYM files on non-macOS systems, maybe we should try that first even on macOS, and only fall back to using Spotlight if that doesn't work?

Done and I also extended it to work for cargo, which doesn't put the dSYM in the same dir as the executable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants