snare / voltron

A hacky debugger UI for hackers
MIT License
6.18k stars 414 forks source link

Cannot work properly on MacOS #181

Closed crazbot closed 7 years ago

crazbot commented 7 years ago

im working on macOS Sierra at version 10.12.1. the following is the execution log while working with install.sh `crazbot:voltron harrse$ ./install.sh

crazbot commented 7 years ago

i have tried hard and finally found that voltron must install with the default python environment. and now a new problem occurred: it will take a long time to load Voltron while the ~/.lldbinit presents. and after it echoed that Voltron loaded the subsequent voltron commands does not take any effects. i am wondering... any help will be appreciated.

snare commented 7 years ago

To fix your first problem, you need to install the pip module for Python.

Yes, Voltron needs to be installed into the same Python installation that the debugger is linked with (per the documentation).

When Voltron is loaded in LLDB can you connect views per the README? What do you mean by "subsequent voltron commands does not take any effects"?

crazbot commented 7 years ago

thank you at first. :D "subsequent voltron commands does not take any effects" i mean the voltron command in lldb does not start any view,, but i d found that the views must start in a new terminal, and it will connect the voltron server initialized in lldb. now it works perfectly. really great tool it is. very appreciate for your job.

spyroot commented 7 years ago

Did you find a solution ?. In my case when I start second terminal I see it try to bind to a same port server.

error: [Errno 48] Address already in use


voltron.server.start()

File "/usr/local/lib/python2.7/site-packages/voltron/core.py", line 162, in start run_listener('tcp', ThreadedVoltronWSGIServer, list(voltron.config.server.listen.tcp) + [self.app]) File "/usr/local/lib/python2.7/site-packages/voltron/core.py", line 154, in run_listener s = cls(*arg)

snare commented 7 years ago

Please open a new issue @spyroot and describe exactly what you are doing in each terminal