Re: [lldb-dev] Symbolicate user processes when kernel debugging

2016-06-22 Thread John Otter via lldb-dev
> "I want a GDB server port for user space process 123" How would I start this gdb server? Do you mean a gdb-server running in the target userspace? Wouldn't that make impossible to use it when the kernel is stopped? I tried searching around and the only resources I found is this old macros file

Re: [lldb-dev] GetSymbolContext(lldb.eSymbolContextEverything)

2016-06-22 Thread Kamenee Arumugam via lldb-dev
Thanks a lot Greg for your input. I have tried the 2nd option to parse the out of image lookup command and it works perfectly fine for me. Regards, Kamenee On Tue, Jun 21, 2016 at 2:21 PM, Greg Clayton wrote: > We currently don't expose this information through the API, though we > could. You

[lldb-dev] Variable shadowing

2016-06-22 Thread Bogdan Hopulele via lldb-dev
Hi all, I'm using lldb 3.9 through the C++ API and I'm trying to determine if a local variable is shadowed or not with no luck. For the code below: 1. Is there an API call, that I somehow missed, that can tell me that (v = 2) shadows (v = 1)? 2. Can I rely on their order in the SB

[lldb-dev] Remote debugging - unix socket and/or specific port

2016-06-22 Thread Adrien Duermael via lldb-dev
Hi, I’ve been trying to run lldb-server from within a linux container lately. When I try to attach from outside the container using lldb command, most steps are successful but I can’t launch the process: platform select remote-linux πŸ‘ platform connect connect://IP:PORT πŸ‘ target create main πŸ‘

[lldb-dev] lldb mutex debugging command

2016-06-22 Thread ?????????? via lldb-dev
Dear all you know, in windbg there is a very useful command -- locks . it will tell us who owned the special lock. in lldb, there is no such command. sometimes, we have a deadlock. but we cannot find the mutex, whitch thread owned it , and do not release!! Thank you very much!

[lldb-dev] lldb mutex debugging command

2016-06-22 Thread ?????????? via lldb-dev
Dear all you know, in windbg there is a very useful command -- locks . it will tell us who owned the special lock. in lldb, there is no such command. sometimes, we have a deadlock. but we cannot find the mutex, whitch thread owned it , and do not release!! Thank you very much!

[lldb-dev] Remote debugging - unix socket and/or specific port

2016-06-22 Thread Adrien Duermael via lldb-dev
Hi, I’ve been trying to run lldb-server from within a linux container lately. When I try to attach from outside the container using lldb command, most steps are successful but I can’t launch the process: platform select remote-linux πŸ‘ platform connect connect://IP:PORT πŸ‘ target create main πŸ‘

Re: [lldb-dev] Symbolicate user processes when kernel debugging

2016-06-22 Thread Greg Clayton via lldb-dev
> On Jun 22, 2016, at 3:38 AM, John Otter wrote: > >> "I want a GDB server port for user space process 123" > > How would I start this gdb server? Do you mean a gdb-server running in > the target userspace? Wouldn't that make impossible to use it when the > kernel is stopped? No, the python sc

Re: [lldb-dev] Variable shadowing

2016-06-22 Thread Greg Clayton via lldb-dev
You can currently do this by checking for other variables to see if any names match. In python when stopped in the function below you can do use the API: (lldb) script Python Interactive Interpreter. To exit, type 'quit()', 'exit()' or Ctrl-D. >>> frame_vars = lldb.frame.GetVariables(True, True

Re: [lldb-dev] Variable shadowing

2016-06-22 Thread Greg Clayton via lldb-dev
The logic is a bit wrong in my script, it should first print out the variables we have already found, followed by the one we are currently processing. The fixed script is attached: #!/usr/bin/python import lldb import shlex @lldb.command("check-shadow") def check_shadow_command(debugger, comma

[lldb-dev] lldb 3.8 on OSX unable to debug process

2016-06-22 Thread Pierson Lee (PIE) via lldb-dev
Hi I'm building LLDB v3.8 on my osx mac using Unix Makefiles and when I go and test it with the built debugserver, I get the following errors when passing "run": error: process exited with status -1 (unable to attach) I verified that attaching to a process also doesn't work. Is there a known