Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 1 tagged
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: 3e83e4f5f249a0f3974c37070051cd29fafc0614 clang+llvm-5.0.0-rc1-aarch64-linux-gnu.tar.xz 2f5baefae0b84b314c1f71e865fbd3093184e800 clang+llvm-5.0.0-rc1-armv7a-linux-gnueabihf.tar.xz Cheers, Diana On 28 July 2017 at 08:43, Sylvestre Ledru via Release-testers wrote: > Hello, > > I am experiencing a build issue with clang tools extra that I reported here: > > https://bugs.llvm.org/show_bug.cgi?id=33970 > > Does it ring a bell? > > Thanks > > S > > > > Le 27/07/2017 à 00:41, Hans Wennborg via Release-testers a écrit : >> Dear testers, >> >> 5.0.0-rc1 has just been tagged. >> >> Please build, test and upload binaries to the sftp. Let me know if >> there are any issues. >> >> I'll upload sources, docs, and your binaries to the pre-release >> website once they're ready. >> >> Thanks, >> Hans >> ___ >> Release-testers mailing list >> release-test...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > > ___ > Release-testers mailing list > release-test...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] Disable shared lib loading
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.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] PDB symbol reader status?
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 able to get the rest of windows support implemented as i got pulled off to add support for writing codeview/pdb to clang-cl On Wed, Jul 26, 2017 at 5:38 PM Vadim Chugunov wrote: > Why -fuse-ld=lld? What does lld do differently than MS linker? > > > On Wed, Jul 26, 2017 at 1:10 PM, Zachary Turner > wrote: > >> For clang-cl you need to use -fuse-ld=lld. For msvc only a small amount >> of pdb support was added to lldb, namely the ability to resolve file and >> line info. >> On Wed, Jul 26, 2017 at 12:46 PM Vadim Chugunov >> wrote: >> >>> I'm trying to use LLDB built from svn trunk: for MSVC emitted binaries >>> it cannot set any breakpoints, and for clang-cl outputs it crashes when >>> setting a breakpoiint by file/line. Are these scenarios supposed to work? >>> WinDbg works fine in both cases, so the debug info is probably ok. >>> >>> (I'm using VS 2017 Build Tools, if that matters). >>> >>> On Wed, Jul 26, 2017 at 11:54 AM, Adrian McCarthy >>> wrote: >>> Basic PDB support is in LLDB if you're running on Windows. LLDB has a SymbolFilePDB plugin that relies on a PDB abstraction in LLVM. There is currently just one implementation of that abstraction, and it relies on DIA, which is a Microsoft-provided DLL on Windows for looking up information in a PDB. I'm currently working on a native PDB reader that implements the same interface without reliance on DIA, so that should eventually provide the same functionality even if you're not running on Windows. Browsing through the PDB plugin in LLDB, I see a lot of "//TODO: Implement this" methods, so you won't (yet) have rich type information. But you can set breakpoints by name, get a stack backtrace, print variable values, etc. On Wed, Jul 26, 2017 at 11:19 AM, Vadim Chugunov via lldb-dev < lldb-dev@lists.llvm.org> wrote: > Hi, > What is the current status of LLDB's PDB file parser on Windows? It > was announced back in 2015 that PDB support is coming soon, so I was > wondering where it's at currently. > > > ___ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev > > >>> > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-dev Digest, Vol 86, Issue 26
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@lists.llvm.org >Subject: Re: [lldb-dev] Remote debugging - unix socket and/or specific port > >Hi Mark, > >A quick look at PlatformPOSIX.cpp, PlatformLinux.cpp >and PlatformRemoteGDBServer.cpp shows that Pavel's description of port >forwarding situation is still accurate. On Linux currently there is no way >to know the port number before LLDB tries actually attach to something. > >Mentioning of GDB server protocol shouldn't confuse you, it's just a name >of a text protocol LLDB client uses to talk to LLDB server [1]. LLDB tries >to be compatible with GDB in this aspect. > > >[1] https://sourceware.org/gdb/onlinedocs/gdb/Remote-Protocol.html -- Mark Nelson – ma...@ieee.org - http://marknelson.us ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] Remote debugging - unix socket and/or specific port
"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://lists.llvm.org/pipermail/lldb-dev/2016-June/010616.html > > It is pretty clear that that the remote-linux platform is trying to > open additional ports to talk to lldb-server, and if that server is > in a container we need to expose them. But what ports, how many, how > to specify? All uncertain. > > Looking at the source shows there are some (undocumented?) port > commands in lldb-server platform, I'm wondering if this is a solved > problem that just doesn't have an easy-to-search-for solution. Hi Mark, There's another thread here: http://lists.llvm.org/pipermail/lldb-dev/2017-February/012004.html where I had an issue connecting to a remote lldb-server process on a particular port. As part of that I was using options to tell lldb-server what ports to use. (I submitted a fix for the connection issues but the options code was written by someone else.) There's some examples of the options in that thread but I did have a summary in my own archives: Option (short and long forms) Purpose --port-offset , -p Specify an offset to return to the port number returned for a new process. --gdbserver-port -PReturn the specified port number when a process is started. (Can specify multiple ports to use using more than one, e.g. -P 1024 -P 2048 ) --min-gdbserver-port -mReturn a port number equal to or greater than the specified port number when a process is started. --max-gdbserver-port -MReturn a port number less than the specified port number when a process is started. I hope that helps, Howard Hellyer IBM Runtime Technologies, IBM Systems Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [llvm-dev] [5.0.0 Release] Release Candidate 1 tagged
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 time. > > Regards, > Andrew > > On Jul 27, 2017 1:42 AM, "Hans Wennborg via llvm-dev" > wrote: > > Dear testers, > > 5.0.0-rc1 has just been tagged. > > Please build, test and upload binaries to the sftp. Let me know if > there are any issues. > > I'll upload sources, docs, and your binaries to the pre-release > website once they're ready. > > Thanks, > Hans > ___ > LLVM Developers mailing list > llvm-...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > > ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] PDB symbol reader status?
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 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 able to get the rest of windows support > implemented as i got pulled off to add support for writing codeview/pdb to > clang-cl > On Wed, Jul 26, 2017 at 5:38 PM Vadim Chugunov wrote: > >> Why -fuse-ld=lld? What does lld do differently than MS linker? >> >> >> On Wed, Jul 26, 2017 at 1:10 PM, Zachary Turner >> wrote: >> >>> For clang-cl you need to use -fuse-ld=lld. For msvc only a small amount >>> of pdb support was added to lldb, namely the ability to resolve file and >>> line info. >>> On Wed, Jul 26, 2017 at 12:46 PM Vadim Chugunov >>> wrote: >>> I'm trying to use LLDB built from svn trunk: for MSVC emitted binaries it cannot set any breakpoints, and for clang-cl outputs it crashes when setting a breakpoiint by file/line. Are these scenarios supposed to work? WinDbg works fine in both cases, so the debug info is probably ok. (I'm using VS 2017 Build Tools, if that matters). On Wed, Jul 26, 2017 at 11:54 AM, Adrian McCarthy wrote: > Basic PDB support is in LLDB if you're running on Windows. LLDB has a > SymbolFilePDB plugin that relies on a PDB abstraction in LLVM. There is > currently just one implementation of that abstraction, and it relies on > DIA, which is a Microsoft-provided DLL on Windows for looking up > information in a PDB. > > I'm currently working on a native PDB reader that implements the same > interface without reliance on DIA, so that should eventually provide the > same functionality even if you're not running on Windows. > > Browsing through the PDB plugin in LLDB, I see a lot of "//TODO: > Implement this" methods, so you won't (yet) have rich type information. > But you can set breakpoints by name, get a stack backtrace, print variable > values, etc. > > > On Wed, Jul 26, 2017 at 11:19 AM, Vadim Chugunov via lldb-dev < > lldb-dev@lists.llvm.org> wrote: > >> Hi, >> What is the current status of LLDB's PDB file parser on Windows? It >> was announced back in 2015 that PDB support is coming soon, so I was >> wondering where it's at currently. >> >> >> ___ >> lldb-dev mailing list >> lldb-dev@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev >> >> > >> ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
