Re: [lldb-dev] No machine instructions loaded for symbols or target (python api)

2015-11-17 Thread kwadwo amankwa via lldb-dev
ndexes to a std::vector, then sort the vector of address indexes, and then we can do the above fixups. Greg Clayton On Nov 17, 2015, at 4:21 AM, kwadwo amankwa via lldb-dev wrote: Hi, I'm building an application on windows using the python api. I need to be able to access a code symbols ins

[lldb-dev] No machine instructions loaded for symbols or target (python api)

2015-11-17 Thread kwadwo amankwa via lldb-dev
Hi, I'm building an application on windows using the python api. I need to be able to access a code symbols instructions but when I launch the process the symbol has no instructions. I can manually read the symbols address space but the symbol also has no end_addr set which makes it difficult

Re: [lldb-dev] How to disassemble a section (python api)?

2015-11-13 Thread kwadwo amankwa via lldb-dev
: symbol_section = symbol.GetStartAddress().GetSection() if symbol_section.GetName() == section_name: print symbol instructions = symbol.GetInstructions(lldb.target) for inst in instructions: print inst On Nov 12, 2015, at 2:1

Re: [lldb-dev] How to disassemble a section (python api)?

2015-11-13 Thread kwadwo amankwa via lldb-dev
Name() == section_name: print symbol instructions = symbol.GetInstructions(lldb.target) for inst in instructions: print inst On Nov 12, 2015, at 2:13 PM, kwadwo amankwa via lldb-dev wrote: Hi I'm writing a small scr

[lldb-dev] How to disassemble a section (python api)?

2015-11-12 Thread kwadwo amankwa via lldb-dev
Hi I'm writing a small script and need to disassemble a whole section , what would be the correct way to go about it ? Cheers Que, ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-07 Thread kwadwo amankwa via lldb-dev
cking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but with a ninja build, your directory will be organized like this:

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-07 Thread kwadwo amankwa via lldb-dev
Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but with a ninja bui

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
on in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but with a ninja build, your directory will be organized like this: build |___b

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
On 05/10/15 16:56, Zachary Turner wrote: Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS201

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
On 05/10/15 16:56, Zachary Turner wrote: Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but

Re: [lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
If this is a debug build, lldb.pyd if release I'm betting you're missing the pyd file. Can you confirm? Then we can diagnose that if it turns out to be the problem. On Mon, Oct 5, 2015 at 5:20 AM kwadwo amankwa via lldb-dev mailto:lldb-dev@lists.llvm.org>> wrote:

[lldb-dev] Fwd: Re: " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
5 16:56, Zachary Turner wrote: Are you using MSBuild or Ninja to build (i.e. are you clicking the Build Solution button in Visual Studio or running ninja from command line)? I don't know where it puts this stuff with a VS2013 build, but with a ninja build, your direc

[lldb-dev] " Import error: No module named embedded_interpreter" on windows

2015-10-05 Thread kwadwo amankwa via lldb-dev
Hi guys, Can someone point me in the right direction on this . I have managed to set up my environment on windows , compiling python2.7.10 using VS2013 and building llvm/lldb in VS2013. lldb and all its libraries build successfully so its just when I import lldb into my python project I get t