Thanks, I know that dwarf works with lldb on Windows, but I was
specifically trying to debug a program compiled with pdb debug info.
(Why not a native Windows debugger? Because I have existing code that uses
lldb api.)
On Fri, Jul 28, 2017 at 4:10 AM, Zachary Turner wrote:
> It can handle linki
I've replied on the patch. It needs to find a reviewer.
On Fri, Jul 28, 2017 at 4:16 AM, Andrew Kelley wrote:
> Hans,
>
> Apologies for the repetition. I'm not quite familiar with the release
> process. Will https://reviews.llvm.org/D35387 make it in? It has been
> awaiting review for quite some
"lldb-dev" wrote on 24/07/2017 16:19:19:
> From: Mark Nelson via lldb-dev
> To: lldb-dev@lists.llvm.org
> Date: 24/07/2017 16:19
> Subject: [lldb-dev] Remote debugging - unix socket and/or specific port
> Sent by: "lldb-dev"
>
> Has there been any change in this since reported here :
>
> http
Thanks for the verification Eugene.
I guess for the short term I am going to look at hacking the source to
force the use of a specific port - this might get us around the blocking
issue.
>Date: Thu, 27 Jul 2017 19:22:46 -0700
>From: Eugene Zemtsov via lldb-dev
>To: Mark Nelson
>Cc: lldb-dev@l
It can handle linking dwarf debug info. Also I misspoke, you can't get
dwarf debug info with clang-cl, but you can with clang++ on windows. Look
at how the test suite on windows compiles the inferiors. That's currently
the best debugging experience of Windows programs.
Unfortunately i was never ab
Hello
I am debugging an program which depends a huge set of shared libs. For
performance i like to skip shlib load on lldb if possible.
Is there any way to do it?
BR,
Lee
나의 iPhone에서 보냄
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.l
Hi,
ARM and AArch64 ready.
Both fail in libunwind_01.pass.cpp and libunwind_02.pass.cpp
(PR33858). In addition, ARM has a failure in libunwind's
alignment.pass.cpp (also PR33858), and AArch64 has one in the
sanitizers, allocator_oom_test (PR33972).
sha1sums:
3e83e4f5f249a0f3974c37070051cd29fafc0
