similar to: [LLVMdev] Trying to build lldb on linux

Hi, I build llvm+clang+lldb 3.7 successfully on centos7, and lldb -p PID works pretty well. However when I tried lldb -c corefile executable_bin, lldb itself core dumpped. Attached the following core info which is debugged by gdb: [root at dn-cn-controller-4fbd4 data1]# lldb -c a.corefile /usr/local/myproject/bin/cnode *(lldb) target create "/usr/local/myproject/bin/cnode" --core

On Sat, Mar 26, 2016 at 11:31 PM, Jeffrey Tan <jeffrey.fudan at gmail.com> wrote: > Thanks David. I meant to send to lldb maillist, but glad to hear response > here. > > Our binary is built from gcc: > String dump of section '.comment': > [ 1] GCC: (GNU) 4.9.x-google 20150123 (prerelease) > > Is there any similar flags we should use? > If it's

Thanks David. I meant to send to lldb maillist, but glad to hear response here. Our binary is built from gcc: String dump of section '.comment': [ 1] GCC: (GNU) 4.9.x-google 20150123 (prerelease) Is there any similar flags we should use? By doing "strings -a [binary] | grep -i gcc", I found the following flags being used: GNU C++ 4.9.x-google 20150123 (prerelease)

Hi, While dogfooding our lldb based IDE on Linux, I am seeing a lot of variable evaluation errors related to DW_TAG_member which prevents us from release the IDE. Can anyone help to confirm if they are known issues? If not, any information you need to troubleshoot this issue? Here is one example: (lldb) fr v *error: biggrep_master_server_async 0x10b9a91a: DW_TAG_member '_M_pod_data'

Hi, I get build errors when trying to build a fresh r139985. Anyone got a clue? carl at carl:~/Downloads/llvm3.0/llvm$ gcc --version gcc (Ubuntu/Linaro 4.5.2-8ubuntu4) 4.5.2 Copyright (C) 2010 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. carl at

If you're going to use clang built binaries with lldb, you'll want to pass -fstandalone-debug - this is the default on platforms where lldb is the primary debugger (Darwin and freebsd) Not sure if that is the problem you are seeing, but will be a problem sooner or later On Mar 26, 2016 4:16 PM, "Jeffrey Tan via llvm-dev" <llvm-dev at lists.llvm.org> wrote: > Hi, >

I'm trying to build llvm and clang release_34 git branch on ubuntu 13.04, using cmake, and i'm getting numerous errors from lldb: [ 83%] Building CXX object tools/lldb/source/Core/CMakeFiles/lldbCore.dir/Address.cpp.o /home/sam/src/llvm/tools/lldb/source/Expression/ClangExpressionParser.cpp: In function ‘clang::FrontendAction* CreateFrontendBaseAction(clang::CompilerInstance&)’:

FYI, this turned out to be an error of omission in LLDB in SymbolFileDWARF, because the case of a non-defining external (i.e. a static member variable) wasn't being handled with a variable lookup to dig up the location. I'll put a patch together for lldb-commits, - Ashok From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Thirumurthi, Ashok

So, when performing expression evaluation, lldb trips over an assert in clang/lib/AST/RecordLayoutBuilder because ExternalFieldOffsets doesn't contain a FieldDecl that updateExternalFieldOffset expected. I found that the assert occurs when both static and non-static member variables are present. For instance, with the following, the lldb command 'expr my_test.length()' does not

hi, I just downloaded llvm3.0 source, and compile it with cmake+msvc2008 ,but failed. the error message was missing X86GenRegisterInfo.inc such kind of files. I can build llvm2.9 with cmake+msvc2008 well, why can't I build llvm3.0 with same method. thanks

Hi Olaf, On Fri, Sep 11, 2009 at 5:24 AM, Olaf Krzikalla <Olaf.Krzikalla at tu-dresden.de> wrote: > Hi @clang, > > I'm somewhat puzzled about using rtti when building clang under gcc (gcc > 4.3.3, linux/ubuntu). > (There is no problem under MSVC since rtti seems to be active there anyway). > The appropriate line 348 in llvm/makefile.rules is commented out meaning >

Hi @llvm, I've already asked the following questions to the clang dev list but got no response. Maybe there is a wider audience at llvmdev and someone here can help me. The question actually boils down to: How can I compile clang with rtti enabled? And this was my original mail (with some points now better explained) to clang: <--BEGIN--> Hi @clang, I'm somewhat puzzled about

To elaborate a bit more on the issue that is detailed in https://reviews.llvm.org/rL260308: There are many clang AST contexts that are used in LLDB: - one for each lldb_private::Module that contains type definitions as we know them in the module and its symbol vendor - one for each expression - one for results of expressions in the lldb_private::Target As we run expressions we end up copying

$(llvm-config --libs | tr " " "\n" | grep gtest) returns: -lgtest_main -lgtest instead of non-valid: -lLLVMgtest_main -lLLVMgtest It also fixes: $(ld): cannot find -lLLVMgtest $(ld): cannot find -lLLVMgtest_main --- unittests/Makefile.unittest | 2 +- utils/llvm-build/llvmbuild/componentinfo.py | 4 ++-- utils/llvm-build/llvmbuild/main.py |

Bill Wendling wrote: > Hi Jack, > > Because of the new changes and the fact that we have only 2 days > before branching for 2.5, please retest the Fortran front end as soon > as you can to see if the problem has been resolved. Hi Bill. Thanks for working on this! Unfortunately, I'm getting this warning now: $ llvm-g++ helloworld.c cc1plus: warning: -Wformat-security

On Wed, Apr 28, 2010 at 9:23 AM, Yuri <yuri at tsoft.com> wrote: > Pekka Jääskeläinen wrote: >> >> On 04/28/2010 11:42 AM, Yuri wrote: >>> >>> Looks like this is platform dependent. >> >> Yep, works fine here on Debian 5.0/x86_64 with gcc 4.3.2. >> >> Did you build with make REQUIRES_RTTI=1 which is required >> as of LLVM 2.7 to

thx my actual RPM failed at the same place .. the below was actually not the result of an rpmbuild command .. cleared out the BUILD directory, untar'd, configure and ran make manually - failed at the same spot as the RPM package .. given 2.2.30.1 built ok saw no reason why 2.2.30.2 should suddenly stop .. rgds Matt > Peter <mailto:peter at pajamian.dhs.org> > 7 June 2017 at

my linux server is redhat AS 3 update 5. I download dovecot 0.99.11 source rpm to rebuild a binary rpm package I issued command rpmbuild -ba dovecot.spec after a few mins of works, rpmbuild process stopped with errors .............. gcc -DHAVE_CONFIG_H -I. -I. -I../.. -O2 -g -pipe -march=i386 -mcpu=i686 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts

On 04/28/2010 11:42 AM, Yuri wrote: > Looks like this is platform dependent. Yep, works fine here on Debian 5.0/x86_64 with gcc 4.3.2. Did you build with make REQUIRES_RTTI=1 which is required as of LLVM 2.7 to get RTTI for LLVM symbols? -- Pekka

From: Gonglei <arei.gonglei at huawei.com> In order to support to assign a boot order for vhost-scsi device, we should get the tpgt for user level (such as Qemu). and at present, we only support the minimum tpgt can boot. Signed-off-by: Gonglei <arei.gonglei at huawei.com> Signed-off-by: Bo Su <subo7 at huawei.com> --- drivers/vhost/scsi.c | 41