[lldb-dev] [Bug 25300] New: Certain environment variables crash lldb-server

https://llvm.org/bugs/show_bug.cgi?id=25300 Bug ID: 25300 Summary: Certain environment variables crash lldb-server Product: lldb Version: 3.7 Hardware: PC OS: Linux Status: NEW Severity: normal

[lldb-dev] [Bug 25296] New: LLDB have a lof of strict aliasing violation (based on GCC warnings)

https://llvm.org/bugs/show_bug.cgi?id=25296 Bug ID: 25296 Summary: LLDB have a lof of strict aliasing violation (based on GCC warnings) Product: lldb Version: unspecified Hardware: PC OS: Linux

Re: [lldb-dev] llvm assertion while evaluating expressions for MIPS on Linux

Hi Greg, Thanks for your reply. There are different temporary symbols for different architectures and file formats. As far as I could see, llvm::MCAsmInfo class has a member "PrivateGlobalPrefix" which specifies this temporary symbol. The default value for PrivateGlobalPrefix is 'L' (for ELF

[lldb-dev] PSA: Python "print" statement disabled in trunk

If you sync to tip, you will pull in r251121, which disables the use of the print statement in Python. This is because in Python 3, the print statement has been removed in favor of the print function. You will see that that the top of every file, the line "from __future__ import print_function"

Re: [lldb-dev] [BUG?] Confusion between translation units?

I guess LLDB was just helping your resolve build issues and make your product better... :-) Let us know how things go once you get your build fixed. Greg > On Oct 23, 2015, at 9:45 AM, Ramkumar Ramachandra wrote: > > Hi, > > On Wed, Oct 21, 2015 at 2:27 PM, Greg Clayton

Re: [lldb-dev] llvm assertion while evaluating expressions for MIPS on Linux

What happens if we go with "_$" as our private prefix? Or maybe "lldb$"? Would this avoid the issue and fix things for MIPS? I would rather us have a consistent private naming scheme across all architectures. Let me know if you can try that out and let us know if this works. Greg > On Oct 23,