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

debug envoy on MacOS with lldb/gdb #3826

Closed
neicunlideyu opened this issue Jul 10, 2018 · 7 comments
Closed

debug envoy on MacOS with lldb/gdb #3826

neicunlideyu opened this issue Jul 10, 2018 · 7 comments
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently

Comments

@neicunlideyu
Copy link

neicunlideyu commented Jul 10, 2018

I want to debug envoy on MacOS, so I take following actions:

  1. I build envoy binary with command bazel build -c dbg --apple_generate_dsym //source/exe:envoy-static
  2. lldb -p {pidOfEnvoy}, set breakpoint breakpoint set --name onConnectionEvent

but the source code doesn't show when break point is hit. Is this supported on MacOS with bazel build? If supported, what option should I add to build phrase?

What's more, can I debug envoy with Xcode?

@neicunlideyu neicunlideyu changed the title debug envoy on MacOS with lldb/gdb with source code attached debug envoy on MacOS with lldb/gdb Jul 10, 2018
@mattklein123 mattklein123 added the question Questions that are neither investigations, bugs, nor enhancements label Jul 10, 2018
@mattklein123
Copy link
Member

@zuercher ?

@zuercher
Copy link
Member

Last I looked bazel does not preserve the dsym files for c++ code and without those files lldb cannot do source level debugging.

I expect using Xcode would have the same problem, but I've not tried.

There's a workaround suggested in bazelbuild/bazel#2537. I don't know if anyone's tried it, though I plan to give it a whirl the next time I want a debugger.

@stale
Copy link

stale bot commented Aug 9, 2018

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Aug 9, 2018
@zuercher zuercher added the help wanted Needs help! label Aug 9, 2018
@stale stale bot removed the stale stalebot believes this issue/PR has not been touched recently label Aug 9, 2018
@mattklein123 mattklein123 removed help wanted Needs help! labels Jan 11, 2019
@stale
Copy link

stale bot commented Feb 10, 2019

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.

@stale stale bot added the stale stalebot believes this issue/PR has not been touched recently label Feb 10, 2019
@stale
Copy link

stale bot commented Feb 17, 2019

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.

@stale stale bot closed this as completed Feb 17, 2019
@drao9
Copy link
Contributor

drao9 commented Feb 19, 2019

I have this working. Hope this helps. https://medium.com/@dirao/debugging-envoyproxy-on-osx-a3ebe87dc916

@acpower7
Copy link

^thanks, but doesn't work for latest version of babel (0.23)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Questions that are neither investigations, bugs, nor enhancements stale stalebot believes this issue/PR has not been touched recently
Projects
None yet
Development

No branches or pull requests

5 participants