For what it's worth, we've been using lldb with ds2 to do remote
debugging on Windows (x86) and Windows Phone (arm) and the lldb side
of things works well with remote Windows targets. Besides porting
lldb-server to Windows there shouldn't be any extra effort on the lldb
side to do what Greg is
> cheers,
> pl
>
> On 1 December 2016 at 07:57, Stephane Sezer via lldb-dev
> <lldb-dev@lists.llvm.org> wrote:
>>
>> For what it's worth, we've been using lldb with ds2 to do remote
>> debugging on Windows (x86) and Windows Phone (arm) and the lldb side
>&
Which set of env vars did you want the child process to inherit? The env
vars of the platform process on the remote?
On Wed, Jul 5, 2017 at 8:47 AM Christopher Book via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi, I'm remote debugging to linux (platform select remote-linux), and then
>
What's the specific use case that you're trying to support with error
messages in the protocol? My initial thought on this is that it's not
really the debug server's job to generate human-readable error messages and
that the debugger is better suited to do the job.
Can this problem be solved by
ningful by keeping a common table. But that would
> only work for lldbserver.
>
> Jim
>
>
> > On Jun 21, 2017, at 4:18 PM, Stephane Sezer via lldb-dev <
> lldb-dev@lists.llvm.org> wrote:
> >
> > What's the specific use case that you're trying to support wit
Can confirm, x86_64 Windows debugging with DWARF works. We use it to debug
some fairly large binaries in production.
On Thu, Nov 2, 2017 at 2:07 PM Zachary Turner via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hello,
>
> I think it mostly works. i686-pc-windows-msvc + DWARF should definitely
