Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-04-03 Thread Eran Ifrah via lldb-dev
I managed to "launch" the process - but it crashes immediately. This happens both with lldb.exe and with my GUI interface See http://pastebin.com/9ep130EQ for detailed backtrace Thanks On Fri, Apr 1, 2016 at 6:31 AM, Zachary Turner wrote: > I will have another look

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-31 Thread Zachary Turner via lldb-dev
I will have another look tomorrow. On Thu, Mar 31, 2016 at 11:56 AM Eran Ifrah wrote: > Ping... > > On Mon, Mar 28, 2016 at 10:19 PM, Eran Ifrah wrote: > >> Sorry, the current status is that lldb-server is no longer needed, >> however the debuggee

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-31 Thread Eran Ifrah via lldb-dev
Ping... On Mon, Mar 28, 2016 at 10:19 PM, Eran Ifrah wrote: > Sorry, the current status is that lldb-server is no longer needed, however > the debuggee process hangs and the lldb.exe is "froze" (i.e. it does not > accept user input) > > Here is the backtrace:

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
Sorry, the current status is that lldb-server is no longer needed, however the debuggee process hangs and the lldb.exe is "froze" (i.e. it does not accept user input) Here is the backtrace: http://pastebin.com/mbLFgCA6 I will try and get lldb built in debug mode for better debugging... but this

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
I was able to locate the problematic code: ProcessWindowsLive::Initialize() was not called due to wrong macros http://reviews.llvm.org/D18520 On Mon, Mar 28, 2016 at 9:31 PM, Eran Ifrah wrote: > Done. > > http://reviews.llvm.org/D18519 > > > On Mon, Mar 28, 2016 at 9:28

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
Done. http://reviews.llvm.org/D18519 On Mon, Mar 28, 2016 at 9:28 PM, Zachary Turner wrote: > Almost, there's one more step. Click Create a New Revision on that > screen, then give it a title and a description. For reviewers put zturner, > and for subscribers put

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Zachary Turner via lldb-dev
Almost, there's one more step. Click Create a New Revision on that screen, then give it a title and a description. For reviewers put zturner, and for subscribers put lldb-commits On Mon, Mar 28, 2016 at 11:20 AM Eran Ifrah wrote: > Is this what you meant: >

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
Is this what you meant: http://reviews.llvm.org/differential/diff/51809/ Thanks On Mon, Mar 28, 2016 at 8:58 PM, Zachary Turner wrote: > For the patch, can you create an account on reviews.llvm.org, and upload > your patch there? This makes interactive reviewing /

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Zachary Turner via lldb-dev
If you compile with MSVC or Clang-cl it wouldn't ask for lldb-server. So most likely there is some code that is using #if defined(_MSC_VER) when it should be using #if defined(LLVM_ON_WINDOWS). You'll have to hunt that down, but a good starting point might be to put a breakpoint in

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Zachary Turner via lldb-dev
For the patch, can you create an account on reviews.llvm.org, and upload your patch there? This makes interactive reviewing / commenting much easier. Let me know if you need help getting that set up. On Mon, Mar 28, 2016 at 10:58 AM Zachary Turner wrote: > If you compile

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
On Mon, Mar 28, 2016 at 6:56 PM, Zachary Turner wrote: > Patches welcome. If you can split it into independent pieces that would be > helpful, but it's not always possible. > > Patch is attached, I think you will find it quite straight forward - feel free to comment and send

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Zachary Turner via lldb-dev
Patches welcome. If you can split it into independent pieces that would be helpful, but it's not always possible. The NativeProcessProtocol error, that's the interface that converts debugging events that occur on the inferior into packets that can be sent to the server, and vice versa. Since

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Eran Ifrah via lldb-dev
On Mon, Mar 28, 2016 at 6:10 PM, Zachary Turner wrote: > I'm the main Windows maintainer, Hi ​ > and while We've gotten things working pretty well on Windows, our effort > has been 100% on building with msvc and/or clang-cl. Building with mingw > has a different set of pre

Re: [lldb-dev] LLDB /w Windows and MinGW64

2016-03-28 Thread Zachary Turner via lldb-dev
I'm the main Windows maintainer, and while We've gotten things working pretty well on Windows, our effort has been 100% on building with msvc and/or clang-cl. Building with mingw has a different set of pre processor defines and some other subtle differences, so it doesn't surprise me that things

[lldb-dev] LLDB /w Windows and MinGW64

2016-03-27 Thread Eran Ifrah via lldb-dev
Hi, I have built LLDB on Windows 7 using MinGW64/4.9.2 (took some effort to get the job done...) When I tried to debug a simple hello world executable, I get this output: D:\software\msys-for-clang\1.0\home\PC\build-release-64-lldb\bin>lldb.exe HelloWorld.exe (lldb) target create