Re: [lldb-dev] RFC: -flimit-debug-info + frame variable

2020-07-21 Thread Pavel Labath via lldb-dev
On 20/07/2020 23:25, Jim Ingham wrote: > It seems like you are having to work hard in the ValueObject system because > you don’t want to use single AST Type for the ValueObject’s type. Seems like > it be much simpler if you could cons up a complete type in the > ScratchASTContext, and then use

[lldb-dev] Break setting aliases...

2020-07-21 Thread Jim Ingham via lldb-dev
When we were first devising commands for lldb, we tried to be really parsimonious with the one & two letter unique command strings that lldb ships with by default. I was trying to leave us as much flexibility as possible as we evolved, and I also wanted to make sure we weren’t taking up all the

Re: [lldb-dev] Break setting aliases...

2020-07-21 Thread Jonas Devlieghere via lldb-dev
I don't mind adding the two-letter commands, but I also don't really see the value in being able to say `bs` instead of `b s -y`. Until either becomes muscle memory, both require a little cognitive overhead of thinking "breakpoint set -y" or "breakpoint source". As a user there would be more value

Re: [lldb-dev] Break setting aliases...

2020-07-21 Thread Jim Ingham via lldb-dev
> On Jul 21, 2020, at 11:13 AM, Jonas Devlieghere wrote: > > I don't mind adding the two-letter commands, but I also don't really see the > value in being able to say `bs` instead of `b s -y`. Until either becomes > muscle memory, both require a little cognitive overhead of thinking > "break

Re: [lldb-dev] RFC: -flimit-debug-info + frame variable

2020-07-21 Thread Greg Clayton via lldb-dev
> On Jul 21, 2020, at 9:27 AM, Pavel Labath wrote: > > On 20/07/2020 23:25, Jim Ingham wrote: >> It seems like you are having to work hard in the ValueObject system because >> you don’t want to use single AST Type for the ValueObject’s type. Seems >> like it be much simpler if you could cons

Re: [lldb-dev] Break setting aliases...

2020-07-21 Thread Greg Clayton via lldb-dev
> On Jul 21, 2020, at 10:22 AM, Jim Ingham via lldb-dev > wrote: > > When we were first devising commands for lldb, we tried to be really > parsimonious with the one & two letter unique command strings that lldb ships > with by default. I was trying to leave us as much flexibility as possib

Re: [lldb-dev] Break setting aliases...

2020-07-21 Thread Jim Ingham via lldb-dev
> On Jul 21, 2020, at 2:54 PM, Greg Clayton wrote: > > > >> On Jul 21, 2020, at 10:22 AM, Jim Ingham via lldb-dev >> wrote: >> >> When we were first devising commands for lldb, we tried to be really >> parsimonious with the one & two letter unique command strings that lldb >> ships with

Re: [lldb-dev] RFC: -flimit-debug-info + frame variable

2020-07-21 Thread Jim Ingham via lldb-dev
> On Jul 21, 2020, at 9:27 AM, Pavel Labath wrote: > > On 20/07/2020 23:25, Jim Ingham wrote: >> It seems like you are having to work hard in the ValueObject system because >> you don’t want to use single AST Type for the ValueObject’s type. Seems >> like it be much simpler if you could cons

Re: [lldb-dev] [Release-testers] LLVM 10.0.1-final has been tagged

2020-07-21 Thread Brian Cain via lldb-dev
Uploaded sles12, ubuntu16: $ cat clang+llvm-10.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz.sha256 48b83ef827ac2c213d5b64f5ad7ed082c8bcb712b46644e0dc5045c6f462c231 clang+llvm-10.0.1-x86_64-linux-gnu-ubuntu-16.04.tar.xz $ cat clang+llvm-10.0.1-x86_64-linux-sles12.4.tar.xz.sha256 59f35fc7967b740315ed