Re: [lldb-dev] lldb-mi doesn't work on MS-Windows
If the snapshot is built without python support and normal lldb is running then I would say lldb-mi should run too. Thanks, Abid On Thu, Aug 17, 2017 at 7:37 PM, Ilia K wrote: > Yep, it requires python from some time. > > Guys, how you think is it okay to have such dependency for lldb-mi, or we > should try to get rid of this? > > On Aug 17, 2017 21:11, "Ted Woodward" wrote: > > Looking at the source, I think the failure is in > CMICmnLLDBDebugger::Initialize(). The snapshot is built without debug > info, so I can't debug it. > > lldb.exe in the snapshot is built without python support. I seem to recall > a discussion a few months ago about lldb-mi requiring python; that might be > the issue. > > In any case, we should contact the buildbot owner and arrange for lldb to > be built with python. We could provide one with python and one without. The > one with python would require the user to install the same python that the > bot used to build lldb. > > Ted > > -- > Qualcomm Innovation Center, Inc. > The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a > Linux Foundation Collaborative Project > > > > -Original Message- > > From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Eli > > Zaretskii via lldb-dev > > Sent: Thursday, August 17, 2017 9:20 AM > > To: Ilia K > > Cc: lldb-dev@lists.llvm.org > > Subject: Re: [lldb-dev] lldb-mi doesn't work on MS-Windows > > > > > From: Ilia K > > > Date: Thu, 17 Aug 2017 14:59:01 +0300 > > > Cc: LLDB > > > > > > Did you build it from sources? If yes, please provide your configure > options. > > > > No, I installed the snapshot available from https://llvm.org/builds/. > > (I used the 32-bit binaries from there.) > > ___ > > 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-server link failure with shared library configuration
Hi Peeter,
Why do you have to make the dependency conditional on
BUILD_SHARED_LIBS? If lldbExpression
depends on LLVMRuntimeDyld it should depend on it independently of the
build config.
Also I gave it a try to build lldb using shared libraries locally and I
haven't hit any issue when I used the following command (on Ubuntu
14.04): cmake ../../llvm -G Ninja -DCMAKE_C_COMPILER=clang
-DCMAKE_CXX_COMPILER=clang++ -DCMAKE_BUILD_TYPE=Release
-DBUILD_SHARED_LIBS=true
Are you using some other cmake flags as well? Also can you check the link
command used for the final linking step if it contains LLVMRuntimeDyld
without your change? Can it be just a library ordering issue where some
symbols are dropped before they are used?
Cheers,
Tamas
On Wed, Aug 30, 2017 at 12:50 AM Peeter Joot
wrote:
> Hi Tamas,
>
> I was able to use your suggestion as follows:
>
> diff --git a/source/Expression/CMakeLists.txt
> b/source/Expression/CMakeLists.txt
>
> index 7d9643a..b53b095 100644
>
> --- a/source/Expression/CMakeLists.txt
>
> +++ b/source/Expression/CMakeLists.txt
>
> @@ -2,6 +2,12 @@ if(NOT LLDB_BUILT_STANDALONE)
>
>set(tablegen_deps intrinsics_gen)
>
> endif()
>
>
> +set(LLDB_EXP_DEPS)
>
> +
>
> +if(BUILD_SHARED_LIBS)
>
> + list(APPEND LLDB_EXP_DEPS LLVMRuntimeDyld)
>
> +endif()
>
> +
>
> add_lldb_library(lldbExpression
>
>DiagnosticManager.cpp
>
>DWARFExpression.cpp
>
> @@ -30,6 +36,7 @@ add_lldb_library(lldbExpression
>
> lldbTarget
>
> lldbUtility
>
> lldbPluginExpressionParserClang
>
> +${LLDB_EXP_DEPS}
>
>
>LINK_COMPONENTS
>
> Core
>
> and was able to successfully build the lldb-server.
>
> --
> Peeter
>
>
___
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-server link failure with shared library configuration
Hi Tamas, It looks like lldb-server only fails if I build with a Debug configuration, which I didn't realize until now. In Release configuration, I don't need any changes to CMakefiles and lldb-server links without error. My full build configuration in debug mode was: mkdir lldb50.1708110153 cd lldb50.1708110153 PATH=$PATH:/opt/lzlabs/bin CC=/usr/bin/clang CXX=/usr/bin/clang++ cmake \ -G \ Ninja \ ../llvm \ -DBUILD_SHARED_LIBS=true \ -DLLVM_TARGETS_TO_BUILD='X86' \ -DCMAKE_BUILD_TYPE=Debug \ -DLLVM_ENABLE_ASSERTIONS=TRUE \ -DCMAKE_INSTALL_PREFIX=/home/pjoot/clang/lldb50.1708110153 \ -DLLVM_OPTIMIZED_TABLEGEN=ON \ -DICU_LIBRARY=/opt/lzlabs/lib64 \ -DICU_INCLUDE_DIR=/opt/lzlabs/include Without any changes LLVMRuntimeDyld is not in the lldb-server link list, so this is not an ordering issue. I'm not sure why this ends up as an issue only with Debug. -- Peeter___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] lldb-server link failure with shared library configuration
I tried to build using the following command what should be a reasonably close approximation to the one you used (I don't have ICU installed at the moment) and it still links fine for me: CC=/usr/bin/clang CXX=/usr/bin/clang++ cmake -G Ninja ../../llvm -DBUILD_SHARED_LIBS=true -DLLVM_TARGETS_TO_BUILD='X86' -DCMAKE_BUILD_TYPE=Debug -DLLVM_ENABLE_ASSERTIONS=TRUE -DLLVM_OPTIMIZED_TABLEGEN=ON It would be great to understand what exactly causes the difference between the 2 cases by some sort of bisecting as I see nothing in the source code what would explain this. If changing from -DCMAKE_BUILD_TYPE=Debug to -DCMAKE_BUILD_TYPE=Release fixes the issue then it would be nice to diff the ninja build graph and the different cmake caches to try to figure out where the different starts. Tamas On Wed, Aug 30, 2017 at 12:17 PM Peeter Joot wrote: > Hi Tamas, > > It looks like lldb-server only fails if I build with a Debug > configuration, which I didn't realize until now. In Release configuration, > I don't need any changes to CMakefiles and lldb-server links without > error. My full build configuration in debug mode was: > > mkdir lldb50.1708110153 > > cd lldb50.1708110153 > > PATH=$PATH:/opt/lzlabs/bin > > CC=/usr/bin/clang CXX=/usr/bin/clang++ cmake \ > > -G \ > > Ninja \ > > ../llvm \ > > -DBUILD_SHARED_LIBS=true \ > > -DLLVM_TARGETS_TO_BUILD='X86' \ > > -DCMAKE_BUILD_TYPE=Debug \ > > -DLLVM_ENABLE_ASSERTIONS=TRUE \ > > -DCMAKE_INSTALL_PREFIX=/home/pjoot/clang/lldb50.1708110153 \ > > -DLLVM_OPTIMIZED_TABLEGEN=ON \ > > -DICU_LIBRARY=/opt/lzlabs/lib64 \ > > -DICU_INCLUDE_DIR=/opt/lzlabs/include > Without any changes LLVMRuntimeDyld is not in the lldb-server link list, > so this is not an ordering issue. I'm not sure why this ends up as an > issue only with Debug. > > -- > Peeter > > ___ 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 4 tagged
Hi, ARM and AArch64 uploaded: 64414576baf177aa3de789343399bf662292 clang+llvm-5.0.0-rc4-aarch64-linux-gnu.tar.xz d8a55e393f6277759165ad89d5b0f1b5a540c81b clang+llvm-5.0.0-rc4-armv7a-linux-gnueabihf.tar.xz No new failures. Cheers, Diana On 30 August 2017 at 08:24, Somchai Smythe via llvm-dev wrote: > Download link? > > On 8/30/17, Hans Wennborg via llvm-dev wrote: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look like. >> >> Please test and let me know if there are any issues. >> >> Cheers, >> Hans >> ___ >> LLVM Developers mailing list >> llvm-...@lists.llvm.org >> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev >> > ___ > 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] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged
So far it's just a tag in the svn repository. If you want the source, you can get it from there. In a few days, the tarballs will be uploaded to http://prereleases.llvm.org/5.0.0/ and I'll send a "source and binaries available" email. On Tue, Aug 29, 2017 at 11:24 PM, Somchai Smythe wrote: > Download link? > > On 8/30/17, Hans Wennborg via llvm-dev wrote: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look like. >> >> Please test and let me know if there are any issues. >> >> Cheers, >> 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] [5.0.0 Release] Release Candidate 3 tagged
Hi, I've uploaded the binaries for rc3: SHA256(clang+llvm-5.0.0-rc3-mipsel-linux-gnu.tar.xz)= f682de9375970c3e43b11da94cfbcb38163a79a5a09806ef0198837eefbfc621 SHA256(clang+llvm-5.0.0-rc3-mips-linux-gnu.tar.xz)= 909095eac1ed5a21a5ba7ea5099d56f29576398b8dd7497453c63b2bcafe7874 SHA256(clang+llvm-5.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)= bb75e1c73b5dec292b7a2092c7876413cc8941eb085e84b53cb31b32d0812b94 During testing, I encountered a new failure when compiling for MIPS32r1, an apparent hang when compiling: test-suite.src/MultiSource/Applications/JM/lencod/rdopt.c This issue did not occur for rc2 and I suspect it's related to PR34326 as gdb is giving me stack traces with DACombine and visitSTORE. Running the test-suite through emulation shows a clean result. Otherwise, looks ok here. Thanks, Simon From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg via lldb-dev [lldb-dev@lists.llvm.org] Sent: 25 August 2017 23:52 To: Release-testers Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev Subject: [lldb-dev] [5.0.0 Release] Release Candidate 3 tagged Dear testers, 5.0.0-rc3 was just tagged. This is a release candidate in the real sense: if nothing bad comes up in testing, this is what the release is going to look like. Please build, test and upload binaries to the sftp (use the /data/testers-uploads/ directory) and let me know what issues remain. I know we're a little bit behind schedule, but hopefully we can get to 'final' soon. Cheers, Hans ___ 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] [5.0.0 Release] Release Candidate 3 tagged
On Wed, Aug 30, 2017 at 10:38 AM, Simon Dardis wrote: > > Hi, > > I've uploaded the binaries for rc3: > > SHA256(clang+llvm-5.0.0-rc3-mipsel-linux-gnu.tar.xz)= > f682de9375970c3e43b11da94cfbcb38163a79a5a09806ef0198837eefbfc621 > SHA256(clang+llvm-5.0.0-rc3-mips-linux-gnu.tar.xz)= > 909095eac1ed5a21a5ba7ea5099d56f29576398b8dd7497453c63b2bcafe7874 > SHA256(clang+llvm-5.0.0-rc3-x86_64-linux-gnu-debian8.tar.xz)= > bb75e1c73b5dec292b7a2092c7876413cc8941eb085e84b53cb31b32d0812b94 Thanks! I've added them to the prerelease page. > During testing, I encountered a new failure when compiling for MIPS32r1, an > apparent hang when > compiling: test-suite.src/MultiSource/Applications/JM/lencod/rdopt.c > > This issue did not occur for rc2 and I suspect it's related to PR34326 as gdb > is giving me stack traces > with DACombine and visitSTORE. Running the test-suite through emulation shows > a clean result. Hmm, if it's related to PR34326, I'd expect it to have shown for rc2 as well. But since you say it doesn't show in emulation, maybe it's not completely deterministic. > > From: lldb-dev [lldb-dev-boun...@lists.llvm.org] on behalf of Hans Wennborg > via lldb-dev [lldb-dev@lists.llvm.org] > Sent: 25 August 2017 23:52 > To: Release-testers > Cc: llvm-dev; cfe-dev; openmp-dev (openmp-...@lists.llvm.org); LLDB Dev > Subject: [lldb-dev] [5.0.0 Release] Release Candidate 3 tagged > > Dear testers, > > 5.0.0-rc3 was just tagged. > > This is a release candidate in the real sense: if nothing bad comes up > in testing, this is what the release is going to look like. > > Please build, test and upload binaries to the sftp (use the > /data/testers-uploads/ directory) and let me know what issues remain. > > I know we're a little bit behind schedule, but hopefully we can get to > 'final' soon. > > Cheers, > Hans > ___ > 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] [llvm-dev] [5.0.0 Release] Release Candidate 4 tagged
W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg via llvm-dev napisał: > Hello testers, > > 5.0.0-rc4 was just tagged. > > There were very few changes after rc3, and if nothing unexpected comes > up, this is what the final release will look like. > > Please test and let me know if there are any issues. > Mostly green here on Gentoo. Three test problems left: 1. clang Python bindings are broken due to incomplete commit. I've requested its revert in #34386 [1] since this is not something we can fix without cooperation of the author, and he's not replying. 2. lldb fails a few tests: Failing Tests (4): lldb :: Expr/TestCallStdStringFunction.test lldb :: Expr/TestCallStopAndContinue.test lldb :: Expr/TestCallUserAnonTypedef.test lldb :: Expr/TestCallUserDefinedFunction.test 3. openmp fails a few tests: Failing Tests (2): libomp :: tasking/omp_taskloop_grainsize.c libomp :: worksharing/for/kmp_doacross_check.c I don't think think it's really worth the effort to try to fix 2/3 now. [1]:https://bugs.llvm.org/show_bug.cgi?id=34386 -- Best regards, Michał Górny ___ 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 4 tagged
On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny wrote: > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg > via llvm-dev napisał: >> Hello testers, >> >> 5.0.0-rc4 was just tagged. >> >> There were very few changes after rc3, and if nothing unexpected comes >> up, this is what the final release will look like. >> >> Please test and let me know if there are any issues. >> > > Mostly green here on Gentoo. Three test problems left: > > 1. clang Python bindings are broken due to incomplete commit. I've > requested its revert in #34386 [1] since this is not something we can > fix without cooperation of the author, and he's not replying. :-( That commit was part of rc1-rc3 too, so I'm sad that we're only learning about it now. From your comment it sounds like one of the tests depends on a module that was never committed. How come the test hasn't been failing on our testing and on the bots? Since this is showing so late, and it only breaks a test, not the bindings per se, I don't think it's severe enough to block the release on. Thanks, Hans ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
Re: [lldb-dev] [Release-testers] [5.0.0 Release] Release Candidate 4 tagged
Uploaded rc4 and rc3 for SLES11. No new issues. 5560fd8bf543bf3cdcaf55caef159664bd2749f3 clang+llvm-5.0.0-rc3-linux- x86_64-sles11.3.tar.xz effbb3a69efec75a67566d91dd4a9e685c2df15d clang+llvm-5.0.0-rc4-linux- x86_64-sles11.3.tar.xz On Tue, Aug 29, 2017 at 6:52 PM, Hans Wennborg via Release-testers < release-test...@lists.llvm.org> wrote: > Hello testers, > > 5.0.0-rc4 was just tagged. > > There were very few changes after rc3, and if nothing unexpected comes > up, this is what the final release will look like. > > Please test and let me know if there are any issues. > > Cheers, > Hans > ___ > Release-testers mailing list > release-test...@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/release-testers > -- -Brian ___ 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 4 tagged
W dniu śro, 30.08.2017 o godzinie 15∶22 -0700, użytkownik Hans Wennborg napisał: > On Wed, Aug 30, 2017 at 2:14 PM, Michał Górny wrote: > > W dniu wto, 29.08.2017 o godzinie 16∶52 -0700, użytkownik Hans Wennborg > > via llvm-dev napisał: > > > Hello testers, > > > > > > 5.0.0-rc4 was just tagged. > > > > > > There were very few changes after rc3, and if nothing unexpected comes > > > up, this is what the final release will look like. > > > > > > Please test and let me know if there are any issues. > > > > > > > Mostly green here on Gentoo. Three test problems left: > > > > 1. clang Python bindings are broken due to incomplete commit. I've > > requested its revert in #34386 [1] since this is not something we can > > fix without cooperation of the author, and he's not replying. > > :-( > That commit was part of rc1-rc3 too, so I'm sad that we're only > learning about it now. I'm sorry. I have reported the issue a month ago and was hoping someone would actually reply and fix it. Then I forgot about it. > From your comment it sounds like one of the tests depends on a module > that was never committed. How come the test hasn't been failing on our > testing and on the bots? There are no bots running the Python bindings test suite, and I suppose nobody is actually running them but people who commit new stuff to the checks and Gentoo. > Since this is showing so late, and it only breaks a test, not the > bindings per se, I don't think it's severe enough to block the release > on. > Well, we can always fix it on our end, and hope a fix comes before 5.0.1, or we can revert it then. -- Best regards, Michał Górny ___ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
