libbacktrace
libbacktrace copied to clipboard
Avoid failing early when we cannot find symbols on macho
I've been hitting this issue on macOS where backtrace errors out early even though it can still find symbols for some libraries. This happens when I am loading my library dynamically from python, so I assume its some python libraries that are causing issues.
I'm not quite sure if the logic here is correct. It works in my use cases, but I think I need someone who knows the codebase to verify it is correct.
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!
and we'll verify it.
What to do if you already signed the CLA
Individual signers
- It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.
Corporate signers
- Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
- The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
- The email used to register you as an authorized contributor must also be attached to your GitHub account.
ℹ️ Googlers: Go here for more info.
@googlebot I signed it!
@ianlancetaylor Could you take a look at this. Its a pretty simple fix.