Re: [lldb-dev] Using LLDB API on windows

2017-04-04 Thread Eli Zaretskii via lldb-dev
> From: Russell Greene > Date: Tue, 04 Apr 2017 14:50:23 + > Cc: ted.woodw...@codeaurora.org, lldb-dev@lists.llvm.org > > Well I would guess the main problem is lldb being compiled in a msys > environment which I guess lldb > recognizes to be so posix to try and launch lldb-server. The resul

Re: [lldb-dev] Using LLDB API on windows

2017-04-04 Thread Russell Greene via lldb-dev
Well I would guess the main problem is lldb being compiled in a msys environment which I guess lldb recognizes to be so posix to try and launch lldb-server. The results I gave you are from the mingw-w64-x86_64-lldb package in msys2. Pretty sure mingw and msvc have different ABIs though (at least f

Re: [lldb-dev] Using LLDB API on windows

2017-04-04 Thread Eli Zaretskii via lldb-dev
> Date: Tue, 04 Apr 2017 03:00:21 + > From: Zachary Turner via lldb-dev > > As the person who added most of the support for debugging Windows > executables, I can tell you that I never > tested a MinGW executable (nor was it one of my original goals). It doesn't > entirely surprise me that

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Russell Greene via lldb-dev
oad up your target, then type “target list”. I’d like to see what > plaform it chose, and what the triple is. > > > > -- > > Qualcomm Innovation Center, Inc. > > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > Linux Foundation Collaborative Projec

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Zachary Turner via lldb-dev
gt; -- > > Qualcomm Innovation Center, Inc. > > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > Linux Foundation Collaborative Project > > > > *From:* Russell Greene [mailto:russellgree...@gmail.com] > *Sent:* Monday, April 03, 2017 11:24 AM

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Russell Greene via lldb-dev
t; -- > > Qualcomm Innovation Center, Inc. > > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > Linux Foundation Collaborative Project > > > > *From:* Russell Greene [mailto:russellgree...@gmail.com] > *Sent:* Monday, April 03, 2017 11:24 AM > *To:* Ted

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Russell Greene via lldb-dev
dation Collaborative Project > > > > *From:* Russell Greene [mailto:russellgree...@gmail.com] > *Sent:* Monday, April 03, 2017 11:24 AM > *To:* Ted Woodward ; LLDB < > lldb-dev@lists.llvm.org> > *Subject:* Re: [lldb-dev] Using LLDB API on windows > > > > That makes

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Ted Woodward via lldb-dev
Forum, a Linux Foundation Collaborative Project From: Russell Greene [mailto:russellgree...@gmail.com] Sent: Monday, April 03, 2017 11:24 AM To: Ted Woodward ; LLDB Subject: Re: [lldb-dev] Using LLDB API on windows That makes sense, and I'm sure it works great when using MSVC as a com

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Russell Greene via lldb-dev
That makes sense, and I'm sure it works great when using MSVC as a compiler, but I think LLDB recognizes mingw as a unix compiler and tries to do GDBRemoteCommunication::StartDebugserverProcess when it should be doing PlatformWindows::DebugProcess. Not sure though. All I know is when I try to do a

Re: [lldb-dev] Using LLDB API on windows

2017-04-03 Thread Ted Woodward via lldb-dev
Hi Russell, I assume you mean for SBTarget::Launch or LaunchSimple to launch a Windows application. The short answer is, this already works. SBTarget::Launch calls Target::Launch, which calls DebugProcess in the relevant platform. For cases where we use lldb-server, the platform make