Re: [lldb-dev] announcing an *early preview* of a cross-referencing code search website for LLVM

Nice! Glad to see some work progressing on a UI :-) --Shahms On Thu, Mar 10, 2016 at 11:26 AM, Peter Collingbourne wrote: > Hi, > > I've found that one of the most useful tools in the Chromium project is > its code search website, http://cs.chromium.org/ > > At

Re: [lldb-dev] DWARFASTParserClang and DW_TAG_typedef for anonymous structs

Please file a bug for this and I will relate it to our internal apple bug that tracks this issue. > On Mar 10, 2016, at 2:03 PM, Greg Clayton via lldb-dev > wrote: > > Thanks for the example, this is indeed a new regression. It used to work > (Xcode 7.2), but now

Re: [lldb-dev] DWARFASTParserClang and DW_TAG_typedef for anonymous structs

Thanks for the example, this is indeed a new regression. It used to work (Xcode 7.2), but now with top of tree it doesn't. Sean Callanan recently pulled out a bunch of work around we used to have in the expression/JIT so that we can avoid certain issues that were caused by said work arounds,

Re: [lldb-dev] Not able to find process plugin for core file

> On Mar 10, 2016, at 4:34 AM, Bhushan Attarde via lldb-dev > wrote: > > Hi All, > > I am working on adding support for MIPS coredump file in LLDB. > > I tried below command: > > (lldb) target create "app_mips.elf" --core "core_mips" > error: Unable to find

Re: [lldb-dev] Better error message for attaching to a process already being debugged

> On Mar 9, 2016, at 5:40 PM, Jeffrey Tan wrote: > > Hi Greg, I am using the lldb(/usr/bin/lldb) installed by Xcode not self-built > one. For example, I can use lldb to attach to chrome without any problem. And > I can see the debugserver it uses is from >

[lldb-dev] [Bug 26901] New: LLDB should report meaningful error message during SBTarget creation and launch/attach

https://llvm.org/bugs/show_bug.cgi?id=26901 Bug ID: 26901 Summary: LLDB should report meaningful error message during SBTarget creation and launch/attach Product: lldb Version: 3.8 Hardware: PC OS: Linux

Re: [lldb-dev] DWARFASTParserClang and DW_TAG_typedef for anonymous structs

Hi Greg First of all thanks for taking the time to help out with this. On 10/03/16 00:18, Greg Clayton wrote: So we ran into a problem where we had anonymous structs in modules. They have no name, so we had no way to say "module A, please give me a struct named... nothing in the namespace

Re: [lldb-dev] LLDB + UE4 on Android

Well, after I've added .gnu_debuglink section to stripped libUE4.so LLDB managed to resolve the symbols. But sometimes it asserts with the following message: --- Microsoft Visual C++ Runtime Library --- Assertion failed! Program:

Re: [lldb-dev] What's the purpose of the TestStarted-XXX and TestFinished-XXX files?

Thanks. I have a patch out that removes the files that I'll probably submit today. On Thu, Mar 10, 2016 at 1:44 AM, Pavel Labath wrote: > I don't think anyone is relying on these. We should just stop creating > them altogether. > > We are using the *.log files to track test

[lldb-dev] Not able to find process plugin for core file

Hi All, I am working on adding support for MIPS coredump file in LLDB. I tried below command: (lldb) target create "app_mips.elf" --core "core_mips" error: Unable to find process plug-in for core file '/home/battarde/test/ core_mips' Currently LLDB is not able to find a Process plugin for

Re: [lldb-dev] LLDB + UE4 on Android

Hi Mikhail, Modifying the build tool to include the build ID would probably be the easiest solution to your problem. Please not that both the stripped AND unstripped versions of the module need to have the (same) .note.gnu.build-id section. I am not familiar with the build tool, but "fixing" this